From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <clameter@sgi.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Richard Knutsson <ricknu-0@student.ltu.se>
Subject: Re: [PATCH 1/2] kmemcheck v3
Date: Fri, 08 Feb 2008 08:33:57 +0200 [thread overview]
Message-ID: <47ABF7D5.7040406@cs.helsinki.fi> (raw)
In-Reply-To: <47ABF715.60407@cs.helsinki.fi>
Pekka Enberg wrote:
> No. We need to not track the whole page to avoid recursive faults. So
> for kmemcheck we absolutely do need cache_cache but we can, of course,
> hide that under a alloc_cache() function that only uses the extra cache
> when CONFIG_KMEMCHECK is enabled?
Btw, one option is to have a new _page flag_ so that we no longer need
to look inside struct kmem_cache in the page fault handler.
Pekka
next prev parent reply other threads:[~2008-02-08 6:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 21:36 [PATCH 1/2] kmemcheck v3 Vegard Nossum
2008-02-07 21:39 ` [PATCH 2/2] " Vegard Nossum
2008-02-07 21:53 ` [PATCH 1/2] " Christoph Lameter
2008-02-07 22:12 ` Vegard Nossum
2008-02-07 22:53 ` Christoph Lameter
2008-02-07 23:18 ` Vegard Nossum
2008-02-07 23:32 ` Christoph Lameter
2008-02-08 6:40 ` Pekka Enberg
2008-02-08 8:09 ` Ingo Molnar
2008-02-08 6:30 ` Pekka Enberg
2008-02-08 6:33 ` Pekka Enberg [this message]
2008-02-08 7:10 ` Christoph Lameter
2008-02-08 7:48 ` Pekka Enberg
2008-02-08 11:55 ` Andi Kleen
2008-02-08 11:31 ` Pekka Enberg
2008-02-08 12:10 ` Andi Kleen
2008-02-08 11:39 ` Pekka Enberg
2008-02-08 11:37 ` Pekka Enberg
2008-02-08 12:15 ` Andi Kleen
2008-02-08 11:43 ` Pekka Enberg
2008-02-08 12:18 ` Vegard Nossum
2008-02-08 13:20 ` Andi Kleen
2008-02-08 12:59 ` Vegard Nossum
2008-02-08 13:48 ` Andi Kleen
2008-02-09 9:33 ` Ingo Molnar
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=47ABF7D5.7040406@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ricknu-0@student.ltu.se \
--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