On Fri, 2007-10-26 at 16:48 +0200, Peter Zijlstra wrote: > I appreciate the sysfs people their opinion that /sys/bdi/ might not be the > best from their POV, however I'm not seeing where to hook the BDI object from > so that it all makes sense, a few of the things are currently not exposed in > sysfs at all, like the NFS and FUSE things. What happended to the idea to create a "bdi" class, and have the existing devices as parents, and for stuff that is not (not now, or never) in sysfs, no parent is set. Thanks, Kay - 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/
- Follow-Ups:
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Peter Zijlstra <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- References:
- -mm merge plans for 2.6.24
- From: Andrew Morton <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: "Kay Sievers" <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Peter Zijlstra <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Nick Piggin <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Kay Sievers <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Peter Zijlstra <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Kay Sievers <[email protected]>
- Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- From: Peter Zijlstra <[email protected]>
- -mm merge plans for 2.6.24
- Prev by Date: Re: Is gcc thread-unsafe?
- Next by Date: Re: [PATCH] PCMCIA: prevent auto insert during resume.
- Previous by thread: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- Next by thread: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- Index(es):