PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
View this message in context:
http://www.nabble.com/IO-transfer-limits-tf2953389.html#a8307532
Sent from the linux-scsi mailing list archive at Nabble.com.
-
To unsubscribe from this list: send the line unsubscribe
Douglas Gilbert wrote:
john clyne wrote:
What do the different hostX in /sys/class/scsi_host corespond to? There are
seven hostX directories, 5 with sg_tablesize set to 128 and two set to 255.
A Linux host is a SCSI initiator port (e.g. FC) or a
SCSI initiator device (e.g. SAS). Another way
unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
View this message in context:
http://www.nabble.com/IO-transfer-limits-tf2953389.html#a8284792
Sent from the linux-scsi mailing list archive
Stefan Richter wrote:
Douglas Gilbert wrote:
john clyne wrote:
What do the different hostX in /sys/class/scsi_host corespond to? There are
seven hostX directories, 5 with sg_tablesize set to 128 and two set to 255.
A Linux host is a SCSI initiator port (e.g. FC) or a
SCSI initiator device
Douglas Gilbert wrote:
There are cheap external boxes out there that have 1394,
USB and (e)SATA interfaces. I wonder what would happen
if one tried to use two interfaces connected to different
machines at the same time :-)
AFAIK these are all based on the OXUF924 series of bridge chips. Their
On Thu, 2007-01-11 at 11:48 -0800, john clyne wrote:
So what's the best course of action for increasing the 512kb IO transfer size
limit, changing SCSI_MAX_PHYS_SEGMENTS (currently 128 and apparently can be
set no greater than 256), or increasing the page size? Or is there another
option.
), but I don't see any relevent
parameters. I'm running RHEL 4.0 with a 2.6.9-34 kernel. Any pointers would
be greatly appreciated.
cheers - jc
--
View this message in context:
http://www.nabble.com/IO-transfer-limits-tf2953389.html#a8260533
Sent from the linux-scsi mailing list archive at Nabble.com
john clyne wrote:
Can anyone give me some guidance on where in the IO stack I might be running
into a 512KB limit on IO transfer sizes to an external FC device? I've
checked IO scheduler parameter
(/sys/block/dev/queue/{max_sectors_kb,max_hw_sectors_kb}. Both are set to
32767. I'm using
john clyne wrote:
Can anyone give me some guidance on where in the IO stack I might be running
into a 512KB limit on IO transfer sizes to an external FC device? I've
checked IO scheduler parameter
(/sys/block/dev/queue/{max_sectors_kb,max_hw_sectors_kb}. Both are set to
32767. I'm using
be clustered you will end up with 4K * 128.
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
View this message in context:
http://www.nabble.com/IO-transfer
to several kernel people that there were users out there
that needed larger IO transfer limits. So I suggest that
you talk the the management and tell them why you
need higher limits. Linux is retarded in this area.
Doug Gilbert
Mike Christie wrote:
john clyne wrote:
Can anyone give me some guidance
11 matches
Mail list logo