From: Andi Kleen <ak@suse.de>
To: Erich Focht <efocht@hpce.nec.com>
Cc: LSE <lse-tech@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Lse-tech] Node affine NUMA scheduler extension
Date: Tue, 27 May 2003 11:11:04 +0200 [thread overview]
Message-ID: <20030527091104.GB31510@wotan.suse.de> (raw)
In-Reply-To: <200305271031.55554.efocht@hpce.nec.com>
On Tue, May 27, 2003 at 10:31:55AM +0200, Erich Focht wrote:
> This patch is an adaptation of the earlier work on the node affine
> NUMA scheduler to the NUMA features meanwhile integrated into
> 2.5. Compared to the patch posted for 2.5.39 this one is much simpler
> and easier to understand.
Yes, it is also much simpler than my implementation (I did a similar homenode
scheduler for an 2.4 kernel). The basic principles are the same.
But the main problems I have is that the tuning for threads is very
difficult. On AMD64 where Node equals CPU it is important
to home node balance threads too. After some experiments I settled on
homenode assignment on the first load balance (called "lazy homenode")
When a thread clones it initially executes on the CPU of the parent, but
there is a window until the first load balance tick where it can allocate
memory on the wrong node. I found a lot of code runs very badly until the
cache decay parameter is set to 0 (no special cache affinity) to allow
quick initial migration. Migration directly on fork/clone requires a lot
of changes and also breaks down on some benchmarks.
-Andi
next prev parent reply other threads:[~2003-05-27 8:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 8:31 Erich Focht
2003-05-27 9:11 ` Andi Kleen [this message]
2003-05-27 9:54 ` [Lse-tech] " Erich Focht
2003-05-27 10:01 ` Andi Kleen
2003-05-27 11:39 ` Erich Focht
2003-05-27 11:40 ` Andi Kleen
2003-05-27 11:50 ` Erich Focht
2003-05-27 15:38 ` Martin J. Bligh
2003-05-27 21:28 ` Erich Focht
2003-05-27 21:51 ` Martin J. Bligh
2003-05-28 17:02 ` Erich Focht
2003-05-28 17:13 ` Martin J. Bligh
2003-05-28 18:14 ` Rick Lindsley
2003-05-28 19:32 ` Martin J. Bligh
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=20030527091104.GB31510@wotan.suse.de \
--to=ak@suse.de \
--cc=efocht@hpce.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®