[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <49F1B68D.3010304@garzik.org>
Date: Fri, 24 Apr 2009 08:54:37 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Kay Sievers <kay.sievers@...y.org>
CC: "Martin K. Petersen" <martin.petersen@...cle.com>,
rwheeler@...hat.com, snitzer@...hat.com, neilb@...e.de,
James.Bottomley@...senpartnership.com, dgilbert@...erlog.com,
jens.axboe@...cle.com, matthew@....cx, linux-ide@...r.kernel.org,
linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2 of 9] block: Export I/O topology for block devices and
partitions
Kay Sievers wrote:
> On Fri, Apr 24, 2009 at 07:32, Martin K. Petersen
> <martin.petersen@...cle.com> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists