Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763006AbXJZPeR (ORCPT ); Fri, 26 Oct 2007 11:34:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751966AbXJZPeG (ORCPT ); Fri, 26 Oct 2007 11:34:06 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:45870 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751816AbXJZPeF (ORCPT ); Fri, 26 Oct 2007 11:34:05 -0400 Subject: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24) From: Peter Zijlstra To: Kay Sievers Cc: Nick Piggin , Andrew Morton , linux-kernel@vger.kernel.org, Jens Axboe , Fengguang Wu , greg@kroah.com, Trond Myklebust , Miklos Szeredi In-Reply-To: <1193412788.2431.22.camel@lov.site> References: <20071001142222.fcaa8d57.akpm@linux-foundation.org> <3ae72650710020421t711caaa8o13d2e685a98e5fe8@mail.gmail.com> <1191325226.13204.63.camel@twins> <200710022205.05295.nickpiggin@yahoo.com.au> <1191406506.4093.35.camel@lov.localdomain> <1191407872.5572.7.camel@lappy> <1191418525.4093.87.camel@lov.localdomain> <1193410087.6914.34.camel@twins> <1193411451.2431.13.camel@lov.site> <1193412147.27652.2.camel@twins> <1193412788.2431.22.camel@lov.site> Content-Type: text/plain Date: Fri, 26 Oct 2007 17:33:56 +0200 Message-Id: <1193412836.27652.11.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2031 Lines: 52 On Fri, 2007-10-26 at 17:33 +0200, Kay Sievers wrote: > On Fri, 2007-10-26 at 17:22 +0200, Peter Zijlstra wrote: > > On Fri, 2007-10-26 at 17:10 +0200, Kay Sievers wrote: > > > 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. > > > > Must have forgotten about that, mainly because I'm not sure I fully > > understand it. > > > > So we create a class, > > Yes. > > > create these objects, > > Yes, "struct device" objects, assigned to the "bdi" class. (Don't use > class_device, that will be removed soon.) > > > which are all called bdi > > Probably not. You can name it how you want, you can inherit the name of > the parent, or prefix it with whatever fits, they just need to be > unique. Things like the "fuse-%llu" name would work just fine. I guess > you already solved that problem in the debugfs directory. > > > and have children with these attributes in it. > > The attributes would just be files in the device object. > > > Now, I supposed there is a directory that lists all unparented thingies, > > how do I locate the one that matches my nfs mount? > > You look for the name (prefix), try: "ls /sys/class/sound/", it's the > same model all over the place. Ok, will try that. Is there a 'simple uncluttered' example I could look at to copy from? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/