From: William Lee Irwin III <wli@holomorphy.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Andrew Morton <akpm@digeo.com>, linux-mm@kvack.org
Subject: Re: 2.5.68-mm2
Date: Wed, 23 Apr 2003 05:37:24 -0700 [thread overview]
Message-ID: <20030423123724.GC8939@holomorphy.com> (raw)
In-Reply-To: <200304230808.25387.tomlins@cam.org>
On April 23, 2003 04:20 am, Andrew Morton wrote:
>> . I got tired of the objrmap code going BUG under stress, so it is now in
>> disgrace in the experimental/ directory.
On Wed, Apr 23, 2003 at 08:08:25AM -0400, Ed Tomlinson wrote:
> As far as I see it there are two problems that objrmap/shpte/pgcl
> try to solve. One is low memory pte useage, the second being to
> reduce the rmap fork overhead.
pgcl has no relation to time or space overhead for pagetables or
pte_chains. Its use for highmem is mostly for shrinking mem_map[].
On Wed, Apr 23, 2003 at 08:08:25AM -0400, Ed Tomlinson wrote:
> objrmap helps in both cases but has problem with truncate and
> intoduces a O(n^2) search into the the vm.
> shpte helps a lot with the first problem, and does not seem to do
> much for the second. If I remember correctly it could also be a
> config option.
> pgcl should help with both to some extent but is not ready for prime
> time - yet.
> From comments recently made on lkml I believe that the first problem
> is probably more pressing. What problems need to be resolved with
> each patch?
I don't see that pgcl should help with either; its benefits are
increasing physical memory contiguity (good for io), larger fs
blocksize support (feature), and reduction in the number of objects
manipulated by the VM (mem_map[] size). There are no results either
way showing that it improves or degrades page replacement (and if it
improved it would be only by a linear factor, which does not repair
issues involving quadratic algorithms).
I'd love to claim as many benefits as possible for page clustering,
but these are so far outside its scope I'd like to avoid promising
things it's unlikely to deliver.
IMHO shpte, enhancing objrmap with more advanced spatial algorithms,
pagetable reclamation, and possibly even shoving pte_chains in highmem
are better directions for alleviating the space and/or time overhead of
pte_chains, in no small part because they're direct attacks on the issue.
-- wli
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-04-23 12:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 8:20 2.5.68-mm2 Andrew Morton
2003-04-23 9:59 ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 16:50 ` 2.5.68-mm2 Robert Love
2003-04-23 16:57 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 17:11 ` 2.5.68-mm2 Robert Love
2003-04-24 9:14 ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 12:08 ` 2.5.68-mm2 Ed Tomlinson
2003-04-23 12:37 ` William Lee Irwin III [this message]
2003-04-23 14:25 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 14:51 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 15:14 ` 2.5.68-mm2 Alex Tomas
2003-04-23 21:46 ` 2.5.68-mm2 Andrew Morton
2003-04-23 21:47 ` 2.5.68-mm2 Martin J. Bligh
2003-04-24 3:39 ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 21:13 ` 2.5.68-mm2 Martin J. Bligh
2003-04-24 23:13 ` objrmap (was 2.5.68-mm2) Martin J. Bligh
2003-04-24 3:36 ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 20:24 ` 2.5.68-mm2 Bill Davidsen
2003-04-24 20:33 ` 2.5.68-mm2 Benjamin LaHaise
2003-04-25 17:56 ` 2.5.68-mm2 Bill Davidsen
2003-04-25 18:20 ` 2.5.68-mm2 Randy.Dunlap
2003-04-25 18:27 ` 2.5.68-mm2 Robert Love
2003-04-25 18:49 ` 2.5.68-mm2 Martin J. Bligh
2003-04-26 10:34 ` 2.5.68-mm2 Bill Davidsen
2003-04-26 15:34 ` 2.5.68-mm2 Martin J. Bligh
2003-05-01 6:19 ` [BUG] 2.5.68-mm2 and list.h Alexander Hoogerhuis
2003-05-01 6:31 ` Andrew Morton
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=20030423123724.GC8939@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=tomlins@cam.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