linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	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: Mon, 22 Jul 2002 10:34:07 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0207221029590.3086-100000@imladris.surriel.com> (raw)
In-Reply-To: <3D3BAA5B.E3C100A6@zip.com.au>

On Sun, 21 Jul 2002, Andrew Morton wrote:
> "Martin J. Bligh" wrote:

> > These large NUMA machines should actually be rmap's glory day in the
> > sun.
>
> "should be".  Sigh.  Be nice to see an "is" one day ;)

You asked for a "minimal rmap" patch and you got it. ;)

Bill and I actually have code for many of the things listed
but we haven't submitted it yet exactly because everybody
wanted the code merged in small, manageable chunks.

> Do you think that large pages alone would be enough to allow us
> to leave pte_chains (and page tables?) in ZONE_NORMAL, or would
> shared pagetables also be needed?

Large pages should reduce the page table overhead by a factor
of 1024 (or 512 for PAE) and have the same alignment restrictions
that shared page tables have.

OTOH, shared page tables would allow us to map in chunks smaller
than 4MB ... but at what seems like a pretty horrible locking and
accounting complexity, unless somebody comes up with a smart trick.

Apart from both of these we'll also need code to garbage collect
empty page tables so users can't clog up memory by mmaping a page
every 4 MB ;)

regards,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/		http://distro.conectiva.com/

--
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 13:34 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
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 [this message]
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=Pine.LNX.4.44L.0207221029590.3086-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tomlins@cam.org \
    --cc=torvalds@transmeta.com \
    --cc=wli@holomorphy.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