From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-arch@vger.kernel.org, andrea@qumranet.com, steiner@sgi.com,
cl@linux-foundation.org
Subject: Re: MMU notifiers review and some proposals
Date: Sun, 27 Jul 2008 02:45:20 -0700 [thread overview]
Message-ID: <20080727024520.7dd12bf0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080724143949.GB12897@wotan.suse.de>
On Thu, 24 Jul 2008 16:39:49 +0200 Nick Piggin <npiggin@suse.de> wrote:
> I think everybody is hoping to have a workable mmu notifier scheme
> merged in 2.6.27 (myself included). However I do have some concerns
> about the implementation proposed (in -mm).
>
> I apologise for this late review, before anybody gets too upset,
> most of my concerns have been raised before, but I'd like to state
> my case again and involving everyone.
Nick, having read through this discussion and the code (yet again) I
think I'll go ahead and send it all in to Linus. On the basis that
- the code is fairly short and simple
- has no known bugs
- seems to be needed by some folks ;)
- you already have a protopatch which partially addresses your
concerns and afaik there's nothing blocking future improvements to
this implementation?
And a late-breaking review comment: given that about 0.000000000000001%
of people will actually use mm_take_all_locks(), could we make its
compilation conditional on something? Such as CONFIG_MMU_NOTIFIER?
--
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:[~2008-07-27 9:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 14:39 Nick Piggin
2008-07-25 21:45 ` Andrea Arcangeli
2008-07-26 3:08 ` Nick Piggin
2008-07-26 11:38 ` Andrea Arcangeli
2008-07-26 12:28 ` Nick Piggin
2008-07-26 13:02 ` Andrea Arcangeli
2008-07-26 13:10 ` Nick Piggin
2008-07-26 13:35 ` Andrea Arcangeli
2008-07-27 12:25 ` Nick Piggin
2008-07-26 13:14 ` Nick Piggin
2008-07-26 13:49 ` Andrea Arcangeli
2008-07-27 12:32 ` Nick Piggin
2008-07-30 14:19 ` Christoph Lameter
2008-07-30 14:54 ` Andrea Arcangeli
2008-07-30 15:42 ` Christoph Lameter
2008-07-31 6:14 ` Nick Piggin
2008-07-31 14:19 ` Christoph Lameter
2008-07-26 12:33 ` Nick Piggin
2008-07-26 13:04 ` Nick Piggin
2008-07-26 13:16 ` Andrea Arcangeli
2008-07-27 12:08 ` Nick Piggin
2008-07-25 23:29 ` Jack Steiner
2008-07-26 3:18 ` Nick Piggin
2008-07-27 9:45 ` Andrew Morton [this message]
2008-07-27 12:38 ` Nick Piggin
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=20080727024520.7dd12bf0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrea@qumranet.com \
--cc=cl@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=steiner@sgi.com \
--cc=torvalds@linux-foundation.org \
/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