[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0801021222250.20331@schroedinger.engr.sgi.com>
Date: Wed, 2 Jan 2008 12:25:04 -0800 (PST)
From: Christoph Lameter <clameter@....com>
To: Al Viro <viro@...IV.linux.org.uk>
cc: Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: SLUB sysfs support
On Fri, 28 Dec 2007, Al Viro wrote:
> On Thu, Dec 27, 2007 at 06:19:46PM -0800, Christoph Lameter wrote:
> > nfsd4_delegations? What is this about?
>
> The random lifetimes of user-visible files you create in sysfs.
Well these are symlinks.
> > How do I scan for the symlinks in sysfs?
>
> At which point are you going to do that? AFAICS, the fundamental problem
> is that you
> * have aliases indistinguishable, so kmem_cache_destroy() can't tell
> which one is going away, no matter what
> * have per-alias objects in sysfs
> As the result, you have a user-visible mess in that directory in sysfs.
> And I don't see how you would deal with that - on the "the contents of
> directory changes in so-and-so way when such-and-such operation is
> done", not the implementation details one.
If the alias count of a kmem_cache structure reaches zero then all aliases
can be taken down. At that point we know that no aliases exist anymore.
> BTW, I'm rather sceptical about free use of slabs; keep in mind that their
> names have to be unique with your sysfs layout, so...
What do you mean by free use of slabs? Creation of new slab caches to
avoid the rounding up to order 2 size?
--
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