From: Andrew Morton <akpm@osdl.org>
To: schwidefsky@de.ibm.com
Cc: linux-mm@kvack.org, frankeh@watson.ibm.com, rhim@cc.gatech.edu
Subject: Re: Page host virtual assist patches.
Date: Tue, 25 Apr 2006 01:30:44 -0700 [thread overview]
Message-ID: <20060425013044.19888b02.akpm@osdl.org> (raw)
In-Reply-To: <1145952628.5282.8.camel@localhost>
Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
>
> On Mon, 2006-04-24 at 18:01 -0700, Andrew Morton wrote:
> > Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> > >
> > > The basic idea of host virtual assist (hva) 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.
> >
> > This is pretty significant stuff. It sounds like something which needs to
> > be worked through with other possible users - UML, Xen, vware, etc.
> >
> > How come the reclaim has to be done in the host? I'd have thought that a
> > much simpler approach would be to perform a host->guest upcall saying
> > either "try to free up this many pages" or "free this page" or "free this
> > vector of pages"?
>
> Because calling into the guest is too slow.
So speed it up ;)
> You need to schedule a cpu,
> the code that does the allocation needs to run, which might need other
> pages, etc. The beauty of the scheme is that the host can immediately
> remove a page that is mark as volatile or unused. No i/o, no scheduling,
> nothing. Consider what that does to the latency of the hosts memory
> allocation. Even if the percentage of discardable pages is small, lets
> say 25% of the guests memory, the host will quickly find reusable
> memory. If the vmscan of the host attempts to evict 100 pages, on
> average it will start i/o for 75 of them, the other 25 are immediately
> free for reuse.
Batching can do wonders. What's the expected/typical memory footprint of a
guest versus the machine's total physical memory?
And what's the typical total size of a guest?
Because a 100-page chunk sounds an awfully small work unit for a guest, let
alone for the host.
--
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:[~2006-04-25 8:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 12:34 Martin Schwidefsky
2006-04-25 1:01 ` Andrew Morton
2006-04-25 7:19 ` Nick Piggin
2006-04-25 8:31 ` Martin Schwidefsky
2006-04-25 8:37 ` Andrew Morton
2006-04-25 10:44 ` Martin Schwidefsky
2006-04-25 16:29 ` Andrew Morton
2006-04-25 17:04 ` Martin Schwidefsky
2006-04-25 10:04 ` Nick Piggin
2006-04-25 11:28 ` Martin Schwidefsky
2006-04-25 12:13 ` Nick Piggin
2006-04-25 14:15 ` Martin Schwidefsky
2006-04-26 1:13 ` Nick Piggin
2006-04-26 7:39 ` Martin Schwidefsky
2006-04-26 12:03 ` Hubertus Franke
2006-04-27 20:55 ` jschopp
2006-04-25 8:10 ` Martin Schwidefsky
2006-04-25 8:26 ` Nick Piggin
2006-04-25 10:36 ` Martin Schwidefsky
2006-04-25 10:51 ` Nick Piggin
2006-04-25 12:18 ` Martin Schwidefsky
2006-04-25 8:30 ` Andrew Morton [this message]
2006-04-25 10:43 ` Martin Schwidefsky
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=20060425013044.19888b02.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=frankeh@watson.ibm.com \
--cc=linux-mm@kvack.org \
--cc=rhim@cc.gatech.edu \
--cc=schwidefsky@de.ibm.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