From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>, Dave McCracken <dcm@mccr.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Xen Developers List <xen-devel@lists.xensource.com>
Subject: Re: RFC: Superpage/hugepage performance improvement
Date: Tue, 06 Apr 2010 10:40:52 +0100 [thread overview]
Message-ID: <C7E0C034.FA3D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100406092901.GD15578@whitby.uk.xensource.com>
On 06/04/2010 10:29, "Tim Deegan" <Tim.Deegan@eu.citrix.com> wrote:
>> To make this work I added two mmuext ops, one to mark a superpage and
>> one to unmark it. This change makes a huge performance difference in
>> the hugepage mapping (on the order of 50 times faster).
>
> Plus, presumably, some noticeable difference on a macro benchmark. (I
> expect that's the case but I've been wrong before.)
It's a very good question since we might expect that hugetlbfs users
construct long-lived mappings.
-- Keir
next prev parent reply other threads:[~2010-04-06 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 17:52 RFC: Superpage/hugepage performance improvement Dave McCracken
2010-04-06 9:29 ` Tim Deegan
2010-04-06 9:40 ` Keir Fraser [this message]
2010-04-06 14:12 ` Dave McCracken
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=C7E0C034.FA3D%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Tim.Deegan@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).