Kay Sievers wrote:
On Fri, Apr 24, 2009 at 07:32, Martin K. Petersen
<martin.petersen@xxxxxxxxxx> wrote:
+What: /sys/block/<disk>/alignment
+What: /sys/block/<disk>/<partition>/alignment
+What: /sys/block/<disk>/queue/minimum_io_size
+What: /sys/block/<disk>/queue/optimal_io_size
Wouldn't it be good to include "sector", like the queue files do? The
alignment of a partition could mean many things.
/sys/block/<disk>/sector_alignment
/sys/block/<disk>/<partition>/sector_alignment
And prefixing the io values might be easier to read when they show up
in a group?
/sys/block/<disk>/queue/io_minimum_size
/sys/block/<disk>/queue/io_optimal_size
/sys/block/<disk>/queue/io_...
Why do we need all this syscall overhead just to read individual data items?
Isn't it dumb to require 30 userland syscalls simply to input a
10-member data structure?
netlink looks more and more attractive for anything non-trivial.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
