From: Andi Kleen <ak@suse.de>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Eric Dumazet <dada1@cosmosbay.com>,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: idle task's task_t allocation on NUMA machines
Date: Thu, 18 Aug 2005 23:32:37 +0200 [thread overview]
Message-ID: <20050818213236.GC3953@verdi.suse.de> (raw)
In-Reply-To: <20050818200255.GI8822@bouh.labri.fr>
On Thu, Aug 18, 2005 at 10:02:55PM +0200, Samuel Thibault wrote:
> Samuel Thibault, le Thu 18 Aug 2005 21:49:41 +0200, a ?crit :
> > Eric Dumazet, le Thu 18 Aug 2005 17:18:55 +0200, a ?crit :
> > > I believe IRQ stacks are also allocated on node 0, that seems more serious.
> >
> > For the i386 architecture at least, yes: they are statically defined in
> > arch/i386/kernel/irq.c, while they could be per_cpu.
>
> Hum, but the per_cpu areas for i386 are not numa-aware... I'm wondering:
> isn't the current x86_64 numa-aware implementation of per_cpu generic
> enough for any architecture?
Actually it's broken for many x86-64 configurations now that use SRAT because
we assign the nodes to CPUs only after this code runs. I was considering
to remove it.
-Andi
next prev parent reply other threads:[~2005-08-18 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 14:08 idle task's task_t allocation on NUMA machines Samuel Thibault
2005-08-18 15:18 ` Eric Dumazet
2005-08-18 15:39 ` Samuel Thibault
2005-08-18 17:20 ` Christoph Lameter
2005-08-18 19:49 ` Samuel Thibault
2005-08-18 20:02 ` Samuel Thibault
2005-08-18 21:28 ` [Lse-tech] " Martin J. Bligh
2005-08-18 21:32 ` Andi Kleen [this message]
2005-08-18 18:27 ` Robin Holt
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=20050818213236.GC3953@verdi.suse.de \
--to=ak@suse.de \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=samuel.thibault@ens-lyon.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