From: Christoph Lameter <cl@linux-foundation.org>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] Update Unevictable LRU and Mlocked Pages documentation
Date: Fri, 01 Aug 2008 10:41:05 -0500 [thread overview]
Message-ID: <48932E91.9050208@linux-foundation.org> (raw)
In-Reply-To: <1217601369.6232.16.camel@lts-notebook>
Lee Schermerhorn wrote:
> Really? You think it would be OK to leave maybe gigabytes of mlocked
> pages non-migratable? This would prevent defrag, hotplug, and cpuset
Whatever made you think that I would have that view?
I said that we have sufficient reasons I just do not think these reasons were
given in the document. The main reason was not page migration.
> The rationale that Rik mentioned--common handling, as much as
> possible--was the second reason mentioned in the text. Perhaps my
> wording could use some rework/clarification.
Yes please.
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-08-01 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 21:13 [PATCH] Update Unevictable LRU and Mlocked Pages documentation Lee Schermerhorn
2008-07-31 14:14 ` Christoph Lameter
2008-07-31 14:43 ` Lee Schermerhorn
2008-08-01 13:46 ` Christoph Lameter
2008-08-01 14:06 ` Rik van Riel
2008-08-01 14:16 ` Christoph Lameter
2008-08-01 14:36 ` Lee Schermerhorn
2008-08-01 15:41 ` Christoph Lameter [this message]
2008-08-04 20:05 ` Randy Dunlap
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=48932E91.9050208@linux-foundation.org \
--to=cl@linux-foundation.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=riel@redhat.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.