From: Hubertus Franke <frankeh@watson.ibm.com>
To: Rik van Riel <riel@redhat.com>
Cc: rhim@cc.gateh.edu, virtualization@lists.osdl.org, akpm@osdl.org,
nickpiggin@yahoo.com.au,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/9] Guest page hinting: unused / free pages.
Date: Tue, 12 Sep 2006 20:07:44 -0400 [thread overview]
Message-ID: <45074BD0.3060400@watson.ibm.com> (raw)
In-Reply-To: <45073901.8020906@redhat.com>
Rik van Riel wrote:
> Martin Schwidefsky wrote:
>
>> From: Martin Schwidefsky <schwidefsky@de.ibm.com>
>> From: Hubertus Franke <frankeh@watson.ibm.com>
>> From: Himanshu Raj <rhim@cc.gatech.edu>
>>
>> [patch 1/9] Guest page hinting: unused / free pages.
>>
>> A very simple but already quite effective improvement in the handling
>> of guest memory vs. host memory is to tell the host when pages are
>> free.
>
>
> Would it be an idea to place this interface in-between the
> per-cpu free page lists and the buddy allocator, so we can
> move a batch of pages around at once and do the hinting in
> a batched fashion ?
>
> That way the overhead will be acceptable not just on S390
> (where things are millicoded), but also on hypervisor based
> virtualization like Xen.
>
> Easy enough to pass a vector of pages to the hypervisor.
>
Rik, I thought that what we did.
Martin, I see the code actually does it when the page goes into the hot/cold
list. I can't remember conciously moving to that.
I thought we had a decent hit on the hot/cold, so that bulking makes sense.
Then the interface of bulking could be introduced and for s390 it could internally
be implemented as a sequence of ESSA instruction.
Do you remember the reason why we ended up putting it as part of hot/cold freeing?
-- Hubertus
next prev parent reply other threads:[~2006-09-13 0:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 11:09 [patch 1/9] Guest page hinting: unused / free pages Martin Schwidefsky
2006-09-01 15:33 ` Dave Hansen
2006-09-01 15:43 ` Martin Schwidefsky
2006-09-01 15:56 ` Dave Hansen
2006-09-01 16:05 ` Martin Schwidefsky
2006-09-01 16:10 ` Dave Hansen
2006-09-12 22:47 ` Rik van Riel
2006-09-13 0:07 ` Hubertus Franke [this message]
2006-09-13 1:29 ` Rik van Riel
2006-09-13 8:56 ` Martin Schwidefsky
2006-09-13 12:06 ` Hubertus Franke
2006-09-13 12:45 ` Martin Schwidefsky
2006-09-13 13:06 ` Hubertus Franke
2006-09-13 14:45 ` Rik van Riel
2006-09-13 14:59 ` Martin Schwidefsky
2006-09-13 17:05 ` Hubertus Franke
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=45074BD0.3060400@watson.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rhim@cc.gateh.edu \
--cc=riel@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.osdl.org \
/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).