From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: Erich Focht <efocht@hpce.nec.com>, Andi Kleen <ak@suse.de>,
LSE <lse-tech@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Lse-tech] Node affine NUMA scheduler extension
Date: Wed, 28 May 2003 12:32:13 -0700 [thread overview]
Message-ID: <30280000.1054150332@[10.10.2.4]> (raw)
In-Reply-To: <200305281814.h4SIEgj02186@owlet.beaverton.ibm.com>
> Can you define what you mean by big vs small? I presume you mean RSS?
> There are several factors that come into play here, at least:
>
> 1. RSS (and which bits of this lie on which node)
> 2. CPU utilisation of the task
> 3. Task duration
> 4. Cache warmth
> 5. the current balance situation.
>
> Along the same lines, would it make sense to *permit* imbalances for some
> classes of tasks? It may be worth it, for example, to let three threads
> sharing a lot of data to saturate one cpu because what they lose from
> their self-competition is saved from the extremely warm cache.
>
> So you leave cpu0 at 7 tasks even though cpu1 only has 4, because the 7 are
> "related" and the 4 are "dissimilar"? The equation changes dramatically,
> perhaps, once their is an idle cpu, but if everything is busy does it make
> sense to weight the items in the runqueues in any way?
It'd make sense ... but I think it would be a bitch to implement ;-)
How do you know when it's worth it?
M.
prev parent reply other threads:[~2003-05-28 19:19 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 ` [Lse-tech] " Andi Kleen
2003-05-27 9:54 ` 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 [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='30280000.1054150332@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=efocht@hpce.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=ricklind@us.ibm.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 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®