linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Linux Memory Management <linux-mm@kvack.org>,
	Andrew Morton <akpm@osdl.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [patch] mm: mremap correct rmap accounting
Date: Mon, 29 Jan 2007 20:38:03 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701292029390.20859@blonde.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701291219040.3611@woody.linux-foundation.org>

On Mon, 29 Jan 2007, Linus Torvalds wrote:
> 
> How about:
>  - the current code has worked so far, so there is no way in hell I'll 
>    take a patch for some odd-ball architecture for a theoretical problem 
>    that nobody else cares about for 2.6.20 *anyway* and hasn't been 
>    reported until now (considering that it's apparently been around since 
>    rmap went in).
> 
>  - somebody who cares would explore trying to make page_mapcount work like 
>    page_count, and see if this is a viable approach.
> 
>  - at worst, we can do the Andrew thing, and just forget about the 
>    ZERO_PAGE() multi-page thing. It may well be that even MIPS people 
>    don't care any more, if the particular uarch version that was helped 
>    most isn't very common any more (we can always hope..)

I'm currently thinking the right answer will be to keep the MIPS
multiple ZERO_PAGEs, for their performance benefit, but ditch the
way MIPS moves from one ZERO_PAGE to another in move_pte, trying
desperately to retain that performance benefit across mremap.

It never used to do that, it was something Nick noticed and put
into 2.6.14.  I've the ghost of a memory that at that time he
had some code which was actually relying on ZERO_PAGE(vaddr)
always being the expected ZERO_PAGE for that vaddr.
I'm about to search my old mailboxes.

Hugh

--
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:[~2007-01-29 20:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 14:19 Nick Piggin
2007-01-23 20:55 ` Hugh Dickins
2007-01-23 23:49   ` Nick Piggin
2007-01-29  3:31   ` Nick Piggin
2007-01-29  6:40     ` Andrew Morton
2007-01-29  6:57       ` Nick Piggin
2007-01-29 19:08     ` Hugh Dickins
2007-01-29 19:27       ` Linus Torvalds
2007-01-29 20:03         ` Andrew Morton
2007-01-29 20:18           ` Linus Torvalds
2007-01-29 21:27             ` Ralf Baechle
2007-01-29 20:10         ` Hugh Dickins
2007-01-29 20:22           ` Linus Torvalds
2007-01-29 20:38             ` Hugh Dickins [this message]
2007-01-29 21:24               ` Hugh Dickins
2007-01-30  1:00                 ` Nick Piggin
2007-01-30 14:24                 ` Carsten Otte
2007-01-30 16:41                   ` Ralf Baechle
2007-01-30 17:35                     ` Carsten Otte
2007-01-30 15:47                 ` Carsten Otte
2007-01-30 22:04                   ` Hugh Dickins
2007-01-31 13:51                     ` Carsten Otte
2007-01-31 13:59                     ` Carsten Otte
2007-01-31 16:31                       ` Hugh Dickins
2007-02-01 16:21                         ` Carsten Otte

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=Pine.LNX.4.64.0701292029390.20859@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=ralf@linux-mips.org \
    --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