All of lore.kernel.org
 help / color / mirror / Atom feed
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:23:13 -0400	[thread overview]
Message-ID: <48A2B611.8010904@redhat.com> (raw)
In-Reply-To: <C4C85942.255E6%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> On 13/8/08 09:22, "Tim Deegan" <Tim.Deegan@citrix.com> wrote:
> 
>> At 09:21 +0100 on 13 Aug (1218619274), Jan Beulich wrote:
>>> Both seem to be hacks to get to 128 CPUs, without consideration of how
>>> to go beyond that
>> I think the shadow_page_info one is a general fix for my implicit
>> assumption that sizeof(cpumask_t) == sizeof (long).
> 
> Do some fields after the cpumask need to line up in both structures? Placing
> a dummy cpumask in the shadow_page structure might make most sense.

Yes, there is a check that a field of page_info and a
field of the shadow_page_info are at the same offset.
Both compile time checks are in private.h

> 
> 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.

 Bill


> 
>  -- Keir
> 
> 

  parent reply	other threads:[~2008-08-13 10:23 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 [this message]
2008-08-13 10:25         ` Keir Fraser
2008-08-13 10:53           ` Bill Burns
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=48A2B611.8010904@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.