Sponsored Content
The Lounge What is on Your Mind? How Would You Like Your Loops Served Today? Post 302656421 by jim mcnamara on Thursday 14th of June 2012 04:41:31 PM
Old 06-14-2012
I do not have an opinion, except that the scrutinizer's test is somewhat flawed, IMO:

#1. The speed difference is because of disk controller caching. Try reversing the order the commands are executed.

Or making two identical copies of the file for the test.

#2. ksh93 mmaps files in that syntactic context, and usually means a single full-on 66 MB I/O request which modern controllers can perform on one request. 66MB may well fit in disk controller cache. So that is a valid result - faster.

Also you need to remove the character special I/O:
my take using one of our compellant SAN:
Code:
# uzpplpl_ng02cprd.log.73 is 160MB 

appworx> time cat uzpplpl_ng02cprd.log.73 > /dev/null

real    0m0.02s
user    0m0.00s
sys     0m0.01s

That measures the overhead required do to a single cat. Zilch, IMO. You have to come up with a way to show me that creating one extra child is important to something like this as well.

OTH creating thousands of children for a cat call inside a loop is a very serious issue, which I think is the origin of the entire UUOC thing.
 

4 More Discussions You Might Find Interesting

1. IP Networking

to serve or be served??

I have two machines on my network - one OSX mac and one linux box. The mac is my main workhorse, and the linux box does occasional chores and webserving. Currently the mac shares (via NFS) files with the Liinux box. Would it be less demanding on the mac if I made it a client, and moved my files... (2 Replies)
Discussion started by: mistafeesh
2 Replies

2. Web Development

Symbol Links amongst Apache's served files, is this a security-don't?

I read somewhere that you should make sure Apache is configured to not allow symbolic links to be followed outside the webroot, as this can compromise security. I can imagine how this could lead to a security risk: eg: Is my assumption correct? -- Is it nothing more than: "its just... (0 Replies)
Discussion started by: jzacsh
0 Replies

3. Shell Programming and Scripting

meaning of today=${1:-${today}}

what does today=${1:-${today}} mean??? I saw a script which has these two lines: today=`date '+%y%m%d'` today=${1:-${today}} but both gives the same value for $today user:/export/home/user>today=`date '+%y%m%d'` user:/export/home/user>echo $today 120326... (2 Replies)
Discussion started by: Vidhyaprakash
2 Replies

4. AIX

VIOS backupios -mksysb - does it need to be served by a NIM server ?

working through VIOS backup options. Generally, we store mksysb's on a server and then NFS mount them from it to copy to a VIO optical library, etc. In the case of a VIO backup, I see the -mksysb option to backupios and understand that it doesn't include the NIM resources in the backup. ... (3 Replies)
Discussion started by: maraixadm
3 Replies
HPSA(4) 						     Linux Programmer's Manual							   HPSA(4)

NAME
hpsa - HP Smart Array SCSI driver SYNOPSIS
modprobe hpsa [ hpsa_allow_any=1 ] DESCRIPTION
hpsa is a SCSI driver for HP Smart Array RAID controllers. Options hpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of operating systems from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that would normally be handled by the cciss(4) driver. These older boards have not been tested and are not supported with hpsa, and cciss(4) should still be used for these. Supported hardware The hpsa driver supports the following Smart Array boards: Smart Array P700M Smart Array P212 Smart Array P410 Smart Array P410i Smart Array P411 Smart Array P812 Smart Array P712m Smart Array P711m StorageWorks P1210m Since Linux 4.14, the following Smart Array boards are also supported: Smart Array 5300 Smart Array 5312 Smart Array 532 Smart Array 5i Smart Array 6400 Smart Array 6400 EM Smart Array 641 Smart Array 642 Smart Array 6i Smart Array E200 Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E500 Smart Array P400 Smart Array P400i Smart Array P600 Smart Array P700m Smart Array P800 Configuration details To configure HP Smart Array controllers, use the HP Array Configuration Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time. FILES
Device nodes Logical drives are accessed via the SCSI disk driver (sd(4)), tape drives via the SCSI tape driver (st(4)), and the RAID controller via the SCSI generic driver (sg(4)), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively. HPSA-specific host attribute files in /sys /sys/class/scsi_host/host*/rescan This is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g., hot-plugged tape drives, or newly configured or deleted logical drives, etc.) and notify the SCSI midlayer of any changes detected. Normally a rescan is triggered automatically by HP's Array Configuration Utility (either the GUI or the command-line variety); thus, for logical drive changes, the user should not normally have to use this attribute. This attribute may be useful when hot plugging devices like tape drives, or entire storage boxes containing preconfigured logical drives. /sys/class/scsi_host/host*/firmware_revision This attribute contains the firmware version of the Smart Array. For example: # cd /sys/class/scsi_host/host4 # cat firmware_revision 7.14 HPSA-specific disk attribute files in /sys /sys/class/scsi_disk/c:b:t:l/device/unique_id This attribute contains a 32 hex-digit unique ID for each logical drive. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat unique_id 600508B1001044395355323037570F77 /sys/class/scsi_disk/c:b:t:l/device/raid_level This attribute contains the RAID level of each logical drive. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat raid_level RAID 0 /sys/class/scsi_disk/c:b:t:l/device/lunid This attribute contains the 16 hex-digit (8 byte) LUN ID by which a logical drive or physical device can be addressed. c:b:t:l are the controller, bus, target, and lun of the device. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat lunid 0x0000004000000000 Supported ioctl() operations For compatibility with applications written for the cciss(4) driver, many, but not all of the ioctls supported by the cciss(4) driver are also supported by the hpsa driver. The data structures used by these ioctls are described in the Linux kernel source file include/linux/cciss_ioctl.h. CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD These three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices. This does exactly the same thing as writing to the hpsa-specific host "rescan" attribute. CCISS_GETPCIINFO Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID). CCISS_GETDRIVVER Returns driver version in three bytes encoded as: (major_version << 16) | (minor_version << 8) | (subminor_version) CCISS_PASSTHRU, CCISS_BIG_PASSTHRU Allows "BMIC" and "CISS" commands to be passed through to the Smart Array. These are used extensively by the HP Array Configuration Utility, SNMP storage agents, and so on. See cciss_vol_status at <http://cciss.sf.net> for some examples. SEE ALSO
cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8), <http://cciss.sf.net>, and Documentation/scsi/hpsa.txt and Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source tree COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 HPSA(4)
All times are GMT -4. The time now is 04:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy