From: Daniel Phillips <phillips@bonn-fries.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Momchil Velikov <velco@fadata.bg>,
William Lee Irwin III <wli@holomorphy.com>,
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: Wed, 8 May 2002 18:06:37 +0200 [thread overview]
Message-ID: <E175Txf-0003o9-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44L.0205081143091.32261-100000@imladris.surriel.com>
On Wednesday 08 May 2002 16:43, Rik van Riel wrote:
> On Wed, 8 May 2002, Daniel Phillips wrote:
>
> > To make this concrete, what would copy_page_range look like, using this
> > mechanism?
>
> Or maybe copy_page_range should be behind this mechanism and
> modify the data structures directly ?
It already modifies the data structures directly. You're proposing that
copy_page_range should be per_arch?
> Remember that the goal is not to abstract out all of the VM,
> the goal is to make _most_ of the VM more readable and maintainable.
remap_page_range has the same problem. So which of the bulk memory
operations actually gets cleaner?
If the answer to 'can the proposed api handle copy_page_range?' is 'no', then
it's not a very interesting api. And by 'handling' I don't mean 'make it
per-arch', that's going backwards.
--
Daniel
--
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-08 16:06 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 [this message]
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
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=E175Txf-0003o9-00@starship \
--to=phillips@bonn-fries.net \
--cc=Martin.Bligh@us.ibm.com \
--cc=csmith@micromuse.com \
--cc=jknapka@earthlink.net \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=velco@fadata.bg \
--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 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.