On Mon, Feb 22, 2010 at 6:36 PM, James Bottomley <James.Bottomley@xxxxxxx> wrote: > OK, so now see what max_hw_sectors_kb says ... if it's still 512 and > you're sure you've got sg_tablesize set to something higher, there's > likely something in the USB stack resetting it ... I suppose it's > possible there's something else in your kernel doing that for the > architecture, but you could rule that out by looking at > max_hw_sectors_kb for either a SCSI or libata device and verifying it's > much higher than 512. when I set the max_sectors to 1024 in scsiglue.c(drivers/usb/storage), it reflected as 512 in /sys/block/<dev>/queue/max_sectors_kb and /sys/block/<dev>/queue/max_hw_sectors_kb. If I change the max_sectors to 1536 or 2048 in scsiglue.c file, still it reflected as 512 in /sys/block/<dev>/queue/max_sectors_kb and 768 or 1024 in /sys/block/<dev>/queue/max_hw_sectors_kb. Thanks and Regards, RD -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
