From: Bill Burns <bburns@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: RFC: large system support - 128 CPUs
Date: Wed, 13 Aug 2008 06:53:23 -0400 [thread overview]
Message-ID: <48A2BD23.6080902@redhat.com> (raw)
In-Reply-To: <C4C87530.25614%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 13/8/08 11:23, "Bill Burns" <bburns@redhat.com> wrote:
>
>>> For the other one I'll have to think a bit. The need for GDT entries per CPU
>>> currently obviously means scaling much past a few hundred CPUs is going to
>>> be difficult.
>> Yes, would like something better here. And as I said, we
>> don't know yet that just adding the additional page solves
>> anything.
>
> How many CPUs do you currently need/want to support?
>
Currently just looking to get 128 working.
But would be nice to have some proper sizing,
or even detection of running out. There is a
'last' GDT entry or some such #define, that is
never used (at least in the 3.1 code base).
Bill
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-08-13 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 18:41 RFC: large system support - 128 CPUs Bill Burns
2008-08-13 8:21 ` Jan Beulich
2008-08-13 8:22 ` Tim Deegan
2008-08-13 8:26 ` Keir Fraser
2008-08-13 8:45 ` Jan Beulich
2008-08-13 8:47 ` Keir Fraser
2008-08-13 8:52 ` Keir Fraser
2008-08-13 10:23 ` Bill Burns
2008-08-13 10:25 ` Keir Fraser
2008-08-13 10:53 ` Bill Burns [this message]
2008-08-13 11:15 ` Keir Fraser
2008-08-13 8:21 ` Tim Deegan
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=48A2BD23.6080902@redhat.com \
--to=bburns@redhat.com \
--cc=Tim.Deegan@citrix.com \
--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.