From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: torvalds-3NddpPZAyC0@public.gmane.org,
discuss-Wa75r+71Mmgdnm+yROfE0A@public.gmane.org,
akpm-3NddpPZAyC0@public.gmane.org, "Raj,
Ashok" <ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] [15/105] x86_64: Add documentation for CPU hotplug ACPI extension
Date: Mon, 16 Jan 2006 23:08:58 +0100 [thread overview]
Message-ID: <200601162308.59433.ak@suse.de> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005B83B30-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Monday 16 January 2006 23:02, Brown, Len wrote:
> (corrected Ashok Raj's e-mail address, added linux-acpi).
>
> One problem here is that big systems will not specify
> even all the _present_ CPUs in the MADT -- they'll be
> in the DSDT; as the MADT method I s limited to 256.
The x86 APICs are limited to 256 CPUs anyways, so I don't see
any bigger systems any time soon. Before going to that
size x86 Linux will have many other scaling issues fixed
anyways - for example you can't have more than 256 interrupt
vectors right now and only one per CPU is definitely not
enough. There are other issues like this. I would guess
the practical limit right now is 64 maybe 128 threads
Anyways, DSDT is supported too. We'll use the standard
callback which is AFAIK run by the DSDT too.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2006-01-16 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 22:02 [PATCH] [15/105] x86_64: Add documentation for CPU hotplug ACPI extension Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3005B83B30-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2006-01-16 22:08 ` Andi Kleen [this message]
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=200601162308.59433.ak@suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=discuss-Wa75r+71Mmgdnm+yROfE0A@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-3NddpPZAyC0@public.gmane.org \
/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