From: Dave McCracken <dcm@mccr.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
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 16:43:01 -0500 [thread overview]
Message-ID: <201004301643.01580.dcm@mccr.org> (raw)
In-Reply-To: <C8009B11.11991%keir.fraser@eu.citrix.com>
On Friday 30 April 2010, Keir Fraser wrote:
> One option would be an array of reference counts indexed by superpage
> number (i.e, mfn>>9). So kind of a separate array to page_info, and a
> non-zero superpage refcount would arrange to hold a reference on every
> relevant page in page_info.
>
> 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.
Dave
next prev parent reply other threads:[~2010-04-30 21:43 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 [this message]
2010-04-30 22:03 ` Keir Fraser
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=201004301643.01580.dcm@mccr.org \
--to=dcm@mccr.org \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--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).