linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Ed Tomlinson <tomlins@cam.org>
Subject: Re: [PATCH][1/2] return values shrink_dcache_memory etc
Date: Sun, 21 Jul 2002 22:04:29 -0700	[thread overview]
Message-ID: <3D3B925D.624986EE@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0207201351160.1552-100000@home.transmeta.com>

Linus Torvalds wrote:
> 
> On Sat, 20 Jul 2002, Rik van Riel wrote:
> >
> > OK, I'll try to forward-port Ed's code to do that from 2.4 to 2.5
> > this weekend...
> 
> Side note: while I absolutely think that is the right thing to do, that's
> also the much more "interesting" change. As a result, I'd be happier if it
> went through channels (ie probably Andrew) and had some wider testing
> first at least in the form of a CFT on linux-kernel.
> 

I'd suggest that we avoid putting any additional changes into
the VM until we have solutions available for:

2: Make it work with pte-highmem  (Bill Irwin is signed up for this)

4: Move the pte_chains into highmem too (Bill, I guess)

6: maybe GC the pte_chain backing pages. (Seems unavoidable.  Rik?)


Especially pte_chains in highmem.  Failure to fix this well
is a showstopper for rmap on large ia32 machines, which makes
it a showstopper full stop.

If we can get something in place which works acceptably on Martin
Bligh's machines, and we can see that the gains of rmap (whatever
they are ;)) are worth the as-yet uncoded pains then let's move on.
But until then, adding new stuff to the VM just makes a `patch -R'
harder to do.

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

  parent reply	other threads:[~2002-07-22  5:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-20 19:40 Rik van Riel
2002-07-20 20:11 ` Linus Torvalds
2002-07-20 20:41   ` Rik van Riel
2002-07-20 20:53     ` Linus Torvalds
2002-07-20 21:42       ` Rik van Riel
2002-07-22  5:04       ` Andrew Morton [this message]
2002-07-22  5:16         ` William Lee Irwin III
2002-07-22  5:38           ` Andrew Morton
2002-07-22  6:06             ` Martin J. Bligh
2002-07-22  6:46               ` Andrew Morton
2002-07-22  7:20                 ` Martin J. Bligh
2002-07-22 14:00                   ` Rik van Riel
2002-07-22 13:34                 ` Rik van Riel
2002-07-22 13:44                   ` Rik van Riel

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=3D3B925D.624986EE@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    --cc=tomlins@cam.org \
    --cc=torvalds@transmeta.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