From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: William Lee Irwin III <wli@holomorphy.com>,
Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: 64GB NUMA-Q after pgcl
Date: Mon, 31 Mar 2003 23:02:51 +0200 [thread overview]
Message-ID: <20030331230251.F626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030331052214.GV13178@holomorphy.com>; from wli@holomorphy.com on Sun, Mar 30, 2003 at 09:22:14PM -0800
Hi William,
hi Andrea,
On Sun, Mar 30, 2003 at 09:22:14PM -0800, William Lee Irwin III wrote:
> Miscellaneous side effects happen, like follow_page() and
> get_user_pages() need to return pfn's instead of struct pages.
Hmm, but you know, that users of get_user_pages() play games with
pages? They need to lock them into memory, mark them eventually
dirty, map them to a struct scatterlist and much more.
I worked on an API (I called it the page-walk-api), to make this
more and more transparent.
So if this work will go into 2.6.x, then the page-walk-API will
be needed, or else the driver writers playing tricks with
virtual<->physical<->bus address conversions will go nuts.
So which kernel is the target of this development?
Regards
Ingo Oeser
next prev parent reply other threads:[~2003-03-31 21:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 4:00 64GB NUMA-Q after pgcl William Lee Irwin III
2003-03-28 7:45 ` Zwane Mwaikambo
2003-03-28 7:57 ` William Lee Irwin III
2003-03-28 8:05 ` Zwane Mwaikambo
2003-03-28 10:14 ` William Lee Irwin III
2003-03-28 17:38 ` John Levon
2003-03-30 23:19 ` Andrea Arcangeli
2003-03-31 4:27 ` William Lee Irwin III
2003-03-31 5:22 ` William Lee Irwin III
2003-03-31 21:02 ` Ingo Oeser [this message]
2003-03-31 22:27 ` William Lee Irwin III
2003-04-01 1:25 ` Andrea Arcangeli
2003-03-31 18:35 ` Andrea Arcangeli
2003-03-31 18:41 ` Christoph Hellwig
2003-03-31 19:08 ` William Lee Irwin III
2003-04-01 0:47 ` Andrea Arcangeli
2003-04-01 0:44 ` Andrea Arcangeli
2003-03-31 18:55 ` William Lee Irwin III
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=20030331230251.F626@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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