From: Mick Jordan <Mick.Jordan@sun.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Dave McCracken <dcm@mccr.org>,
Xen Developers List <xen-devel@lists.xensource.com>
Subject: Re: Design question for PV superpage support
Date: Mon, 02 Mar 2009 10:46:03 -0800 [thread overview]
Message-ID: <49AC296B.9080409@Sun.COM> (raw)
In-Reply-To: <C5D1D629.3E2D%keir.fraser@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]
On 03/02/09 10:30, Keir Fraser wrote:
> On 02/03/2009 18:03, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>
>
>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>>>
>>> It'd be nice to fall back to the case of not being able to
>>> guarantee all 2MB
>>> extents are aligned and contiguous. So for example being able
>>> to migrate to
>>> or restore on a system that currently doesn't have enough
>>> contiguous memory.
>>>
>> Well, yes and no. I believe the ONLY reason to use 2MB
>> pages is to achieve a significant performance advantage.
>> And I suspect emulating 2MB "virtual pages" on 4KB physical
>> pages will perform at least slightly worse than just
>> 4KB-on-4KB, true?
>>
>
> If you make this constraint then you risk creating domains that you cannot
> always conveniently restore. Obviously you would allocate 2MB extents
> wherever possible, since that is the whole point of this drawn out exercise.
>
Indeed, performance is the issue, less TLB misses. I'm happy to use 2MB
pages when I can and fall back on 4K when I can't. I just want Xen not
to fall over and save/restore to work.
Mick
[-- Attachment #1.2: Type: text/html, Size: 1773 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-03-02 18:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 13:54 Design question for PV superpage support Dave McCracken
2009-03-02 13:58 ` Keir Fraser
2009-03-02 16:43 ` Mick Jordan
2009-03-02 17:06 ` Keir Fraser
2009-03-02 18:02 ` Mick Jordan
2009-03-02 17:29 ` Dave McCracken
2009-03-02 17:52 ` Keir Fraser
2009-03-02 18:03 ` Dan Magenheimer
2009-03-02 18:30 ` Keir Fraser
2009-03-02 18:46 ` Mick Jordan [this message]
2009-03-02 18:48 ` Dan Magenheimer
2009-03-02 19:04 ` Keir Fraser
2009-03-02 17:45 ` Mick Jordan
2009-03-02 17:54 ` Keir Fraser
2009-03-02 18:00 ` Dave McCracken
2009-03-02 18:14 ` Mick Jordan
2009-03-02 19:14 ` Dave McCracken
2009-03-03 1:37 ` Jeremy Fitzhardinge
2009-03-03 3:59 ` Mick Jordan
2009-03-03 14:33 ` Dan Magenheimer
2009-03-03 17:06 ` Mick Jordan
2009-03-03 17:23 ` Jeremy Fitzhardinge
2009-03-03 18:10 ` Keir Fraser
2009-03-03 17:28 ` Jeremy Fitzhardinge
2009-03-03 18:09 ` Dan Magenheimer
2009-03-03 17:26 ` Jeremy Fitzhardinge
2009-03-03 1:32 ` Jeremy Fitzhardinge
2009-03-03 1:15 ` Jeremy Fitzhardinge
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=49AC296B.9080409@Sun.COM \
--to=mick.jordan@sun.com \
--cc=dan.magenheimer@oracle.com \
--cc=dcm@mccr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.