linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: David Rientjes <rientjes@google.com>
Cc: Glauber Costa <glommer@parallels.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Michal Hocko <mhocko@suse.cz>,
	Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] slab: Ignore internal flags in cache creation
Date: Thu, 27 Sep 2012 13:57:16 +0000	[thread overview]
Message-ID: <0000013a0804637a-82ca7649-bc6c-42ef-9a2c-e79b63f47a23-000000@email.amazonses.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209261810180.7072@chino.kir.corp.google.com>

On Wed, 26 Sep 2012, David Rientjes wrote:

> On Wed, 26 Sep 2012, Christoph Lameter wrote:
>
> > > Nack, this is already handled by CREATE_MASK in the mm/slab.c allocator;
> >
> > CREATE_MASK defines legal flags that can be specified. Other flags cause
> > and error. This is about flags that are internal that should be ignored
> > when specified.
> >
>
> That should be ignored for the mm/slab.c allocator, yes.

Then you are ok with the patch as is?


> > I think it makes sense to reserve some top flags for internal purposes.
> >
>
> It depends on the implementation: if another slab allocator were to use
> additional bits that would be a no-op with mm/slab.c, then this patch
> would be too restrictive.  There's also no requirement that any "internal
> flags" reserved by a slab allocator implementation must be shared in the
> same kmem_cache field as the flags passed to kmem_cache_create() -- it's
> actually better if they aren't since they seldom need to be accessed in
> the same cacheline.

There *are* multiple slab allocators using those bits! And this works for
them. There is nothing too restrictive here. The internal flags are
standardized by this patch to be in the highest nibble.



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-09-27 13:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 11:17 Glauber Costa
2012-09-25 16:26 ` Christoph Lameter
2012-09-26  0:46   ` David Rientjes
2012-09-26  8:43     ` Glauber Costa
2012-09-27  1:16       ` David Rientjes
2012-09-27  6:59         ` Glauber Costa
2012-09-27 22:56           ` David Rientjes
2012-09-28  7:46             ` Glauber Costa
2012-09-28 20:25               ` David Rientjes
2012-09-28 14:12             ` Christoph Lameter
2012-09-28 20:39               ` David Rientjes
2012-09-28 21:20                 ` Christoph Lameter
2012-09-28 23:11                   ` David Rientjes
2012-10-01 17:54                     ` Christoph Lameter
2012-10-01  7:28                 ` Pekka Enberg
2012-10-01  7:58                   ` Glauber Costa
2012-09-27 13:54         ` Christoph Lameter
2012-09-27 22:50           ` David Rientjes
2012-09-28 14:04             ` Christoph Lameter
2012-09-28 20:36               ` David Rientjes
2012-09-26 14:57     ` Christoph Lameter
2012-09-27  1:12       ` David Rientjes
2012-09-27 13:57         ` Christoph Lameter [this message]
2012-09-27 22:52           ` David Rientjes
2012-09-28 14:10             ` Christoph Lameter
2012-09-28 20:30               ` David Rientjes

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=0000013a0804637a-82ca7649-bc6c-42ef-9a2c-e79b63f47a23-000000@email.amazonses.com \
    --to=cl@linux.com \
    --cc=glommer@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=penberg@cs.helsinki.fi \
    --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