linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrea Arcangeli <andrea@qumranet.com>
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: Sat, 26 Jul 2008 14:33:29 +0200	[thread overview]
Message-ID: <20080726123329.GB17958@wotan.suse.de> (raw)
In-Reply-To: <20080726113813.GD21150@duo.random>

On Sat, Jul 26, 2008 at 01:38:13PM +0200, Andrea Arcangeli wrote:
> On Sat, Jul 26, 2008 at 05:08:10AM +0200, Nick Piggin wrote:
> > Anyway, I just voice my opinion and let Andrew and Linus decide. To be
> > clear: I have not found any actual bugs in Andrea's -mm patchset, only
> > some dislikes of the approach.
> 
> Yes, like I said I think this is a matter of taste of what you like of
> the tradeoff. There are disadvantages and advantages in both and if we
> wait forever to please everyone taste, it'll never go in.

And for this item, I think there has been a bit too much emphasis
on pleasing the taste of the drivers and not enough on the core
VM. My concern about adding a new TLB flushing design to core VM
was never taken seriously, for example. Nor was my request for
performance numbers. And I did ask early in the year.

I believe when you don't have any real numbers for justification,
the only sane thing to do is go with the most minimal and simplest
implementation first, and add complexity if/when it can be justified.

--
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>

  parent reply	other threads:[~2008-07-26 12:33 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 [this message]
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=20080726123329.GB17958@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=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=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