From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dave McCracken <dcm@mccr.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Xen Developers List <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Add hypercall to mark superpages to improve performance
Date: Fri, 30 Apr 2010 15:03:22 -0700 [thread overview]
Message-ID: <C800A1BA.1199F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <201004301643.01580.dcm@mccr.org>
On 30/04/2010 14:43, "Dave McCracken" <dcm@mccr.org> wrote:
>> That could be implemented with no extra hypercalls, and I reckon it's
>> probably easier to make this race-free too. Obviously it does have extra
>> code complexity to construct this array (which I suppose needs to be
>> sparse, just like page_info array, in the face of very sparse memory
>> maps). The space overhead (about 8 bytes per 2MB, or 0.0004% of total
>> system memory) would be trivial. Compared with an extra reference count in
>> every page_info, which would have a much higher 0.2% overhead.
>
> I like this idea. I'll look into it.
The algorithm for acquiring a superpage refcount would be something like:
y = superpage_info->count
do {
x = y
if ( x == 0 )
for (each page in super_page)
if (!get_page(page))
goto undo_and_fail;
} while ((y = cmpxchg(&superpage_info->count, x, x+1)) != x);
For destroying a superpage refcount:
y = superpage_info->count
do { x = y } while ((y = cmpxchg(..,x,x-1)) != x);
if (x==1) for (each page in super_page) put_page(page)
I'd actually have two refcounts in superpage struct: one for read-only
mappings and one for read-write mappings. The latter would be updated as
above except for the use of {get,put}_page_and_type() instead of
{get,put}_page().
The other thing to note is that this approach is cheap when updating
superpage refcounts between non-zero values. If regularly
constructing/destroying the *only* superpage mapping of a page, then
obviously you are going to be continually taking the slow path. In that
case, pinning a superpage with new hypercalls as you suggested may have to
be done. It kind of depends on how your workloads interact with the
reference-counting. In any case, you could implement the basic version as
described here, and add hypercalls as a second stage if they turn out to be
needed.
I can help with further details and advice if need be.
-- Keir
next prev parent reply other threads:[~2010-04-30 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 14:33 [PATCH] Add hypercall to mark superpages to improve performance Dave McCracken
2010-04-28 6:58 ` Keir Fraser
2010-04-30 19:43 ` Dave McCracken
2010-04-30 21:30 ` Keir Fraser
2010-04-30 22:10 ` Keir Fraser
2010-04-30 21:34 ` Keir Fraser
2010-04-30 21:43 ` Dave McCracken
2010-04-30 22:03 ` Keir Fraser [this message]
2010-05-02 21:34 ` Dave McCracken
2010-05-02 23:54 ` Keir Fraser
2010-05-03 0:03 ` Keir Fraser
2010-05-03 1:55 ` Dave McCracken
2010-05-03 16:09 ` Keir Fraser
2010-05-03 16:29 ` Keir Fraser
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=C800A1BA.1199F%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=dcm@mccr.org \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.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).