http://bugzilla.kernel.org/show_bug.cgi?id=12207 --- Comment #26 from Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> 2009-04-09 21:08:16 --- On Tue, 7 Apr 2009 bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > Now I attached another patch including more features; > > - returning max_hw_sectors for reading max_sectors Why do you want to do this? The attribute is named "max_sectors", so shouldn't it return the value of max_sectors? > - to limit max_sectors by the special value for usb storage Where did your limit come from? I agree, the value should be limited, but the limit should be 4 GB - 1. Not 8 MB. > I think these features are required. > Of course they are useful for me, I may run my code on many versions of kernel > so max_sectors should be checkable and changeable at anytime. Did you know that max_sectors can also be changed through the block interface? For example, under /sys/block/sda/queue/ you can write to max_sectors_kb and you can read max_hw_sectors_kb. > For addition, my PC can send/recv 4MB block but with 8MB ioctl() will report > ENOMEM. Usually the PC is running with 1GB RAM and increasing RAM is not > effective. You'll have to trace this down by yourself. Alan Stern -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
