[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinQ+3BAEac44-TkiKjG-A5FiYsnXtgpZHi3T=qj@mail.gmail.com>
Date: Fri, 10 Dec 2010 18:51:10 +0100
From: Kay Sievers <kay.sievers@...y.org>
To: Lukas Czerner <lczerner@...hat.com>
Cc: Andreas Dilger <adilger.kernel@...ger.ca>,
Greg KH <gregkh@...e.de>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, tytso@....edu, sandeen@...hat.com,
hch@...radead.org, axboe@...nel.dk
Subject: Re: [RFC PATCH 0/2 v1] Ioctl for reading block queue information
On Fri, Dec 10, 2010 at 15:07, Lukas Czerner <lczerner@...hat.com> wrote:
> On Thu, 9 Dec 2010, Andreas Dilger wrote:
>
>> On 2010-12-09, at 12:20, Greg KH wrote:
>> > On Thu, Dec 09, 2010 at 04:25:35PM +0100, Lukas Czerner wrote:
>> >> For a long time it has been pretty painful to retrieve informations from
>> >> /sys/block/*/queue for particular block device. Not only it is painful
>> >> to retrieve informations within C tool, parsing strings, etc, but one
>> >> have to run into problem even finding the proper path in sysfs.
>> >
>> > What's wrong with using libudev? That should give you all of this
>> > information easily using a .c program without any need to change the
>> > kernel at all.
>
> What's wrong with using libudev ? Well, fist of all I have never heard
> about it:), one can argue this is kind of my fault, and second of all
> the documentation is kind of non-existent (almost).
What else do you need?
http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/
Let me know, we can add it.
Thanks,
Kay
--
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