From: Christoph Lameter <cl@linux.com>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Randy Dunlap <randy.dunlap@oracle.com>,
Nick Piggin <npiggin@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2/2] slub: add Documentation/ABI/testing/sysfs-kernel-slab
Date: Thu, 23 Apr 2009 18:55:31 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0904231854130.26300@qirst.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0904231549130.32736@chino.kir.corp.google.com>
On Thu, 23 Apr 2009, David Rientjes wrote:
> I'm more concerned with the userspace API. You're comfortable with
> letting userspace determine what allocator the kernel is using either by
> testing for the presence of certain slub or slqb-specific files or
> checking the config?
Why would userspace have to test? If the fields have the same semantics
then we are fine.
> That should be fine since there's parity among the files that both
> allocators share, but seems fragile if an allocator adds a file that was
> previously only applicable to the other or the API happens to change.
Right. The newly added file must not be in use by another allocator.
> My thinking was that /sys/kernel/slqb would be a permanent reference point
> that userspace could easily test to determine what API is available.
The API is hopefully generic enought to accomodate all allocators.
next prev parent reply other threads:[~2009-04-23 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 18:38 [patch 1/2] slub: rename cpuslab_flush to cpu_slab_flush David Rientjes
2009-04-23 18:38 ` [patch 2/2] slub: add Documentation/ABI/testing/sysfs-kernel-slab David Rientjes
2009-04-23 18:52 ` Christoph Lameter
2009-04-24 23:26 ` [patch] " David Rientjes
2009-04-27 14:09 ` Christoph Lameter
2009-04-28 11:32 ` Pekka Enberg
2009-04-23 22:26 ` [patch 2/2] " David Rientjes
2009-04-23 22:31 ` Christoph Lameter
2009-04-23 22:52 ` David Rientjes
2009-04-23 22:55 ` Christoph Lameter [this message]
2009-04-24 23:35 ` David Rientjes
2009-04-23 19:39 ` [patch 1/2] slub: rename cpuslab_flush to cpu_slab_flush Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0904231854130.26300@qirst.com \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=randy.dunlap@oracle.com \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®