linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@qumranet.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-arch@vger.kernel.org, steiner@sgi.com,
	cl@linux-foundation.org
Subject: Re: MMU notifiers review and some proposals
Date: Fri, 25 Jul 2008 23:45:52 +0200	[thread overview]
Message-ID: <20080725214552.GB21150@duo.random> (raw)
In-Reply-To: <20080724143949.GB12897@wotan.suse.de>

Hi Nick,

On Thu, Jul 24, 2008 at 04:39:49PM +0200, Nick Piggin 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

Just to be clear, I'm waiting mmu notifiers to showup on Linus's tree
before commenting this as it was all partly covered in the past
discussions anyway, so there's nothing really urgent or new here (at
least for me ;).

It's a tradeoff, you pointed out the positive sides and negative point
of both approaches, and depending which kind of the trade you're
interested about, you'll prefer one or the other approach. Your
preference is the exact opposite of what SGI liked and what we
liked. But all works for us, and all works for GRU (though -mm is
faster for the fast path), but only -mm can be easily later extended
for XPMEM/IB if they ever decide to schedule in the mmu notifier
methods in the future (which may never happen and it's unrelated to
the current patches that don't contemplate sleeping at all and it's
pure luck they can be trivially extended to provide for it).

As your patch shown the changes are fairly small anyway if we later
decide to change in 2.6.28-rc, in the meantime current code in -mm was
heavily tested and all code including kvm and gru has been tested only
with this, and this combined with the fact -mm guarantees the fastest
fast path, I hope we leave any discussion to the 2.6.28-rc merge
window, now it's time to go productive finally!

--
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:[~2008-07-25 21: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 [this message]
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
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=20080725214552.GB21150@duo.random \
    --to=andrea@qumranet.com \
    --cc=akpm@linux-foundation.org \
    --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