From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
jbeulich@suse.com
Subject: Re: [PATCH 3/3] xen: eliminate scalability issues from initial mapping setup
Date: Thu, 4 Sep 2014 13:59:48 +0100 [thread overview]
Message-ID: <54086244.7020601@citrix.com> (raw)
In-Reply-To: <1409834326-29287-4-git-send-email-jgross@suse.com>
On 04/09/14 13:38, Juergen Gross wrote:
> Direct Xen to place the initial P->M table outside of the initial
> mapping, as otherwise the 1G (implementation) / 2G (theoretical)
> restriction on the size of the initial mapping limits the amount
> of memory a domain can be handed initially.
The three level p2m limits memory to 512 GiB on x86-64 but this patch
doesn't seem to address this limit and thus seems a bit useless to me.
David
next prev parent reply other threads:[~2014-09-04 12:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 12:38 [PATCH 0/3] xen: remove memory limits from pv-domains Juergen Gross
2014-09-04 12:38 ` [PATCH 1/3] xen: sync some headers with xen tree Juergen Gross
2014-09-04 12:52 ` Jan Beulich
2014-09-05 8:06 ` Juergen Gross
2014-09-04 12:38 ` [PATCH 2/3] xen: eliminate scalability issues from initrd handling Juergen Gross
2014-09-04 12:52 ` David Vrabel
2014-09-04 14:29 ` Jan Beulich
2014-09-04 14:53 ` [Xen-devel] " David Vrabel
2014-09-05 8:04 ` Juergen Gross
2014-09-04 12:38 ` [PATCH 3/3] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2014-09-04 12:59 ` David Vrabel [this message]
2014-09-04 13:02 ` [Xen-devel] " Andrew Cooper
2014-09-04 14:31 ` Jan Beulich
2014-09-04 14:43 ` Andrew Cooper
2014-09-05 7:55 ` Juergen Gross
2014-09-05 9:05 ` Andrew Cooper
2014-09-05 9:44 ` Juergen Gross
2014-09-04 15:13 ` David Vrabel
2014-09-05 8:03 ` Juergen Gross
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=54086244.7020601@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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).