From: William Lee Irwin III <wli@holomorphy.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Rik van Riel <riel@conectiva.com.br>,
Christian Smith <csmith@micromuse.com>,
Joseph A Knapka <jknapka@earthlink.net>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-mm@kvack.org
Subject: Re: Why *not* rmap, anyway?
Date: Tue, 7 May 2002 14:21:23 -0700 [thread overview]
Message-ID: <20020507212123.GZ15756@holomorphy.com> (raw)
In-Reply-To: <E175Ary-0000Th-00@starship>
On Tue, May 07, 2002 at 09:43:29PM +0200, Daniel Phillips wrote:
> The most obvious place to start are the page table walking operations, of
> which there are a half-dozen instances or so. Bill started to do some
> work on this, but that ran aground somehow. I think you might run into
> the argument 'not broken yet, so don't fix yet'. Still, it would be
> worth experimenting with strategies.
> Personally, I'd consider such work a diversion from the more important task
> of getting rmap implemented.
There are a couple of things I should probably say about my prior efforts.
The plan back then was to hide the pagetable structure from generic code
altogether and allow architecture-specific code to export a procedural
interface totally insulating the core from the structure of pagetables.
This was largely motivated by the notion that the optimal pagetable
structure could be chosen on a per-architecture basis. Linus himself
informed me that there was evidence to the contrary regarding
architecture-specific optimal pagetable structures, and so I abandoned
that effort given the evidence the scheme was pessimal.
I have no plans now to change the standardized structure or to export
a HAT from arch code. OTOH I've faced some recent reminders of what the
code looks like now and believe janitoring may well be in order.
Cheers,
Bill
--
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/
next prev parent reply other threads:[~2002-05-07 21:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 22:27 Why *not* rmap, anyway? Joseph A Knapka
2002-04-22 0:23 ` Martin J. Bligh
2002-04-22 2:13 ` Joseph A Knapka
2002-04-22 5:46 ` Martin J. Bligh
2002-04-23 22:40 ` Christian Smith
2002-04-24 0:46 ` Rik van Riel
2002-04-24 10:50 ` Christian Smith
2002-04-24 14:20 ` Rik van Riel
2002-04-24 14:37 ` Momchil Velikov
2002-04-24 14:52 ` Rik van Riel
2002-04-24 15:16 ` Momchil Velikov
2002-04-24 18:31 ` William Lee Irwin III
2002-04-25 15:19 ` Christian Smith
2002-05-05 19:04 ` Daniel Phillips
2002-05-07 18:37 ` Christian Smith
2002-05-07 19:23 ` Rik van Riel
2002-05-07 19:25 ` William Lee Irwin III
2002-05-07 19:47 ` Daniel Phillips
2002-05-07 19:50 ` William Lee Irwin III
2002-05-07 23:02 ` Daniel Phillips
2002-05-08 0:08 ` William Lee Irwin III
2002-05-08 5:08 ` Andrew Morton
2002-05-08 7:59 ` Momchil Velikov
2002-05-08 14:33 ` Daniel Phillips
2002-05-08 14:43 ` Rik van Riel
2002-05-08 16:06 ` Daniel Phillips
2002-05-08 16:10 ` Rik van Riel
2002-05-07 19:49 ` Rik van Riel
2002-05-07 19:53 ` William Lee Irwin III
2002-05-07 19:43 ` Daniel Phillips
2002-05-07 19:51 ` Rik van Riel
2002-05-07 23:11 ` Daniel Phillips
2002-05-07 21:21 ` William Lee Irwin III [this message]
2002-05-07 23:15 ` Daniel Phillips
2002-05-07 19:37 ` Daniel Phillips
2002-05-07 19:47 ` William Lee Irwin III
2002-05-05 18:38 ` Daniel Phillips
2002-05-05 22:23 ` 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=20020507212123.GZ15756@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=csmith@micromuse.com \
--cc=jknapka@earthlink.net \
--cc=linux-mm@kvack.org \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.