From: David Rientjes <rientjes@google.com>
To: Xiaotian Feng <dfeng@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Matt Mackall <mpm@selenic.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
Dmitry Monakhov <dmonakhov@openvz.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] slab: fix caller tracking on !CONFIG_DEBUG_SLAB && CONFIG_TRACING
Date: Fri, 9 Apr 2010 09:49:05 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1004090947030.10992@chino.kir.corp.google.com> (raw)
In-Reply-To: <4BBEC92B.9060407@redhat.com>
On Fri, 9 Apr 2010, Xiaotian Feng wrote:
> > This doesn't work if the underlying slab allocator doesn't define
> > __kmalloc_node_track_caller() regardless of whether CONFIG_TRACING is
> > enabled or not. SLOB, for example, never defines it, and that's why the
> > conditional exists in the way it currently does.
> >
>
> Sorry, I didn't realized this, can we use (defined(CONFIG_TRACING) &&
> defined(CONFIG_SLAB)) ?
>
The valid configurations are
(CONFIG_SLAB && (CONFIG_DEBUG_SLAB || CONFIG_TRACING)) || CONFIG_SLUB
--
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:[~2010-04-09 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 10:11 Xiaotian Feng
2010-04-08 19:12 ` David Rientjes
2010-04-09 6:28 ` Xiaotian Feng
2010-04-09 16:49 ` David Rientjes [this message]
2010-06-30 9:57 ` [PATCH V2] " Xiaotian Feng
2010-06-30 20:07 ` David Rientjes
2010-07-04 16:50 ` 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.2.00.1004090947030.10992@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=catalin.marinas@arm.com \
--cc=cl@linux-foundation.org \
--cc=dfeng@redhat.com \
--cc=dmonakhov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.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