From: Christoph Lameter <cl@linux.com>
To: Glauber Costa <glommer@parallels.com>
Cc: Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH v3] slab: Ignore internal flags in cache creation
Date: Tue, 2 Oct 2012 18:11:25 +0000 [thread overview]
Message-ID: <0000013a22acdcd4-ba2fbe44-ae66-4b10-86fa-d49d907d9dda-000000@email.amazonses.com> (raw)
In-Reply-To: <1349171968-19243-1-git-send-email-glommer@parallels.com>
On Tue, 2 Oct 2012, Glauber Costa wrote:
> #include <linux/kmemleak.h>
>
> +#define SLAB_AVAILABLE_FLAGS 0xFFFFFFFFUL /* No flag restriction */
> +
> enum stat_item {
I thought the SLAB_AVAILABLE_FLAGS would stand for something meaningful
like the flags supported by an allocator given a kernel config. F.e. SLUB
does not support the debug flags if not compiled with debug.
This looks like it could become material that would fit in mm/slab.h.
There are sets of flags that all allocators have to support (RCU, DMA etc)
and others (like the debug flags) that are optional.
Slob also supports some flags but never any of the debug flags.
--
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>
next prev parent reply other threads:[~2012-10-02 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 9:59 Glauber Costa
2012-10-02 18:11 ` Christoph Lameter [this message]
2012-10-02 19:54 ` 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=0000013a22acdcd4-ba2fbe44-ae66-4b10-86fa-d49d907d9dda-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=penberg@kernel.org \
--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