From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Zachary Amsden <zach@vmware.com>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
akpm@osdl.org, nickpiggin@yahoo.com.au, frankeh@watson.ibm.com,
rhim@cc.gateh.edu
Subject: Re: [patch 0/9] Guest page hinting: cover sheet.
Date: Thu, 14 Sep 2006 10:36:23 +0200 [thread overview]
Message-ID: <1158222983.18478.6.camel@localhost> (raw)
In-Reply-To: <45084524.9090609@vmware.com>
On Wed, 2006-09-13 at 10:51 -0700, Zachary Amsden wrote:
> > Only difference of this patch-set compare to the one posted on linux-mm
> > is that this patch-set is against 2.6.18-rc5-mm1. To go back to Andrews
> > question: is this useful for anybody else in addition to s390
>
> Yes, it is useful for VMware as well. I am looking through the patches
> now, and it looks as if they are useful without any changes needed.
That is good news. The current list of changes we are considering is
1) provide batched state transitions for state changes to unused on page
free, from unused to stable on page allocation and to volatile for
page/swap cache pages. Details are still under discussion but I think it
is doable.
2) Get rid of the PG_state_change page flags bit. Use a hashed lock on
the page index instead
3) Get rid of page_host_discards() by defining PageDiscarded() and
friends conditional on CONFIG_PAGE_STATES.
If you can think of anything else that would help wiht the VMware
implementation let me know.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2006-09-14 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 11:08 [patch 0/9] Guest page hinting: cover sheet Martin Schwidefsky
2006-09-13 17:51 ` Zachary Amsden
2006-09-14 8:36 ` Martin Schwidefsky [this message]
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=1158222983.18478.6.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@osdl.org \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rhim@cc.gateh.edu \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).