From: Ingo Molnar <mingo@elte.hu>
To: Tong Li <tong.n.li@intel.com>
Cc: linux-kernel@vger.kernel.org, Chris Snook <csnook@redhat.com>
Subject: Re: [RFC] scheduler: improve SMP fairness in CFS
Date: Wed, 25 Jul 2007 13:01:59 +0200 [thread overview]
Message-ID: <20070725110159.GA15076@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0707231123080.3239@tongli.jf.intel.com>
* Tong Li <tong.n.li@intel.com> wrote:
> This patch extends CFS to achieve better fairness for SMPs. For
> example, with 10 tasks (same priority) on 8 CPUs, it enables each task
> to receive equal CPU time (80%). [...]
hm, CFS should already offer reasonable long-term SMP fairness. It
certainly works on a dual-core box, i just started 3 tasks of the same
priority on 2 CPUs, and on vanilla 2.6.23-rc1 the distribution is this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7084 mingo 20 0 1576 248 196 R 67 0.0 0:50.13 loop
7083 mingo 20 0 1576 244 196 R 66 0.0 0:48.86 loop
7085 mingo 20 0 1576 244 196 R 66 0.0 0:49.45 loop
so each task gets a perfect 66% of CPU time.
prior CFS, we indeed did a 50%/50%/100% split - so for example on
v2.6.22:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2256 mingo 25 0 1580 248 196 R 100 0.0 1:03.19 loop
2255 mingo 25 0 1580 248 196 R 50 0.0 0:31.79 loop
2257 mingo 25 0 1580 248 196 R 50 0.0 0:31.69 loop
but CFS has changed that behavior.
I'll check your 10-tasks-on-8-cpus example on an 8-way box too, maybe we
regressed somewhere ...
Ingo
next prev parent reply other threads:[~2007-07-25 11:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 18:38 [RFC] scheduler: improve SMP fairness in CFS Tong Li
2007-07-23 20:00 ` Andi Kleen
2007-07-23 21:10 ` Li, Tong N
2007-07-23 21:25 ` Chris Friesen
2007-07-24 9:43 ` Andi Kleen
2007-07-23 23:40 ` Chris Snook
2007-07-24 8:07 ` Chris Snook
2007-07-24 17:11 ` Li, Tong N
2007-07-24 17:07 ` Tong Li
2007-07-24 18:08 ` Chris Snook
2007-07-24 19:47 ` Chris Friesen
2007-07-24 20:39 ` Chris Snook
2007-07-24 20:58 ` Li, Tong N
2007-07-24 21:09 ` Chris Snook
2007-07-24 21:23 ` Chris Friesen
2007-07-24 21:45 ` Chris Snook
2007-07-24 23:33 ` Chris Friesen
2007-07-24 21:06 ` Bill Huey
2007-07-24 21:22 ` Chris Snook
2007-07-24 23:14 ` Bill Huey
2007-07-24 21:12 ` Chris Friesen
2007-07-25 11:01 ` Ingo Molnar [this message]
2007-07-25 12:03 ` Ingo Molnar
2007-07-25 17:23 ` Tong Li
2007-07-25 19:24 ` Ingo Molnar
2007-07-25 20:38 ` Chris Friesen
2007-07-25 20:55 ` Chris Snook
2007-07-25 21:15 ` Li, Tong N
2007-07-25 22:24 ` Chris Snook
2007-07-26 19:00 ` Tong Li
2007-07-26 21:31 ` Ingo Molnar
2007-07-26 22:00 ` Li, Tong N
2007-07-27 1:34 ` Tong Li
2007-07-27 17:16 ` Chris Snook
2007-07-27 19:03 ` Tong Li
2007-07-27 22:20 ` Bill Huey
2007-07-27 23:36 ` Chris Snook
2007-07-28 0:54 ` Bill Huey
2007-07-28 2:59 ` Chris Snook
2007-07-28 19:38 ` Tong Li
2007-07-29 2:40 ` Chris Snook
2007-07-28 19:23 ` Tong Li
2007-07-29 3:01 ` Chris Snook
2007-07-25 18:20 ` Li, Tong N
2007-07-25 19:18 ` Ingo Molnar
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=20070725110159.GA15076@elte.hu \
--to=mingo@elte.hu \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tong.n.li@intel.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