On Tue, Oct 02, 2007 at 01:22:32PM +0200, Kay Sievers wrote: > On 10/2/07, Fengguang Wu <[EMAIL PROTECTED]> wrote: > > On Tue, Oct 02, 2007 at 12:44:21PM +0200, Peter Zijlstra wrote: > > > On Tue, 2007-10-02 at 12:31 +0200, Kay Sievers wrote: > > > > > > > What would be the point in another top-level tree for device > > > > information? All devices you are exporting information for, are > > > > already in the sysfs tree, right? > > > > > > Never did find NFS mounts/servers/superblocks or whatever constitutes a > > > BDI for NFS in there. Same goes for all other networked filesystems for > > > that matter. > > > > And loop/md/dm devices... > > Hmm, /sys/block/mdX, /sys/block/loopX, /sys/block/dm-X are all there today.
Yes, but they have no /queue/ subdir, which (for sda etc.) exports both elevator and bdi variables. Now we want to access these bdi variables... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
