From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-mm@kvack.org, akpm@osdl.org, nickpiggin@yahoo.com.au
Cc: frankeh@watson.ibm.com, rhim@cc.gatech.edu
Subject: Guest page hinting patches.
Date: Thu, 24 Aug 2006 16:29:11 +0200 [thread overview]
Message-ID: <20060824142911.GA12127@skybase> (raw)
Fourth version of the guest page hinting patches. The code has been
polished and another race has been fixed (keep fingers crossed that
is has been that last one this time).
The basic idea of guest page hinting is to give a host system which
virtualizes the memory of its guest systems on a per page basis
usage information for the guest pages. The host can then use this
information to optimize the management of guest pages, in particular
the paging. This optimizations can be used for unused (free) guest
pages, for clean page cache pages, and for clean swap cache pages.
The content of free pages can be replace with zeroes and the content
of clean page cache / swap cache pages can be reloaded by the guest
from the backing store.
There are 9 patches that implement guest page hinting:
1) Guest page state changes for free pages.
2) s390 exploitation of state changes for free pages.
3) Guest page state changes for page cache pages.
4) Guest page state changes for swap cache pages.
5) Keep mlocked pages in stable state.
6) Add support for writable page table entries.
7) Optimization for minor faults.
8) Discarded page list.
9) full s390 architecture support for guest page hinting.
The first two patches are independent from the other seven. These
two just deal with unused/free vs. used/stable pages. The code
starts to get interesting with patch #03..
Any objections against pushing patch #01 and patch #02 into the
-mm tree?
The code runs well on s390 and does nothing for all other archs.
Patches are against 2.6.18-rc4-mm2.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
--
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 reply other threads:[~2006-08-24 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 14:29 Martin Schwidefsky [this message]
2006-08-25 5:03 ` Nick Piggin
2006-08-25 18:52 ` Andrew Morton
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=20060824142911.GA12127@skybase \
--to=schwidefsky@de.ibm.com \
--cc=akpm@osdl.org \
--cc=frankeh@watson.ibm.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rhim@cc.gatech.edu \
/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