From: Yasunori Goto <ygoto@us.fujitsu.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [Lhms-devel] Making hotremovable attribute with memory section[0/4]
Date: Mon, 16 Aug 2004 22:15:51 -0700 [thread overview]
Message-ID: <20040816214017.77A3.YGOTO@us.fujitsu.com> (raw)
In-Reply-To: <1092702436.21359.3.camel@localhost.localdomain>
Hello.
> 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.
Basically, kernel have to wait of completion of I/O.
> Consider
> - Video capture
> - AGP Gart
> - AGP based framebuffer (intel i8/9xx)
I didn't consider deeply about this, because usually
enterprise server doesn't need Video capture feature or AGP.
It is usually controlled from other machine.
If it is really necessary, kernel might have to wait
I/O completion or driver modification is necessary.
> - O_DIRECT I/O
I can use page remmaping method by Iwamoto-san.
(See: http://people.valinux.co.jp/~iwamoto/mh.html#remap)
I guess that many case can be saved by this.
> There are also things like cluster interconnects, sendfile and the like
> involved here.
In sendfile case, kernel will wait too. Sooner or later, it will be
timeout.
Thank you for your comment.
Bye.
--
Yasunori Goto <ygoto at us.fujitsu.com>
--
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 5:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 22:56 Fw: " Yasunori Goto
2004-08-16 23:35 ` Dave Hansen
2004-08-17 0:27 ` Alan Cox
2004-08-17 5:15 ` Yasunori Goto [this message]
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=20040816214017.77A3.YGOTO@us.fujitsu.com \
--to=ygoto@us.fujitsu.com \
--cc=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 \
/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