From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Yasunori Goto <ygoto@us.fujitsu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: Fw: [Lhms-devel] Making hotremovable attribute with memory section[0/4]
Date: Tue, 17 Aug 2004 01:27:23 +0100 [thread overview]
Message-ID: <1092702436.21359.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1092699350.1822.43.camel@nighthawk>
On Maw, 2004-08-17 at 00:35, Dave Hansen wrote:
> In any case, the question of the day is, does anyone have any
> suggestions on how to create 2 separate pools for pages: one
> representing hot-removable pages, and the other pages that may not be
> removed?
How do you define the split. There are lots of circumstances where user
pages can be pinned for a long (near indefinite) period of time and used
for DMA.
Consider
- Video capture
- AGP Gart
- AGP based framebuffer (intel i8/9xx)
- O_DIRECT I/O
There are also things like cluster interconnects, sendfile and the like
involved here.
Alan
--
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:[~2004-08-17 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 22:56 Yasunori Goto
2004-08-16 23:35 ` Dave Hansen
2004-08-17 0:27 ` Alan Cox [this message]
2004-08-17 5:15 ` Yasunori Goto
2004-08-17 9:58 ` Dave Jones
2004-08-17 7:52 ` Fw: " Dave Hansen
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=1092702436.21359.3.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=ygoto@us.fujitsu.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