From: Willy Tarreau <w@1wt.eu>
To: "Li, Tong N" <tong.n.li@intel.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Con Kolivas <kernel@kolivas.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Barnes, Jesse" <jesse.barnes@intel.com>,
William Lee Irwin III <wli@holomorphy.com>,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>,
vatsa@in.ibm.com, balbir@in.ibm.com,
Nick Piggin <npiggin@suse.de>, Bill Davidsen <davidsen@tmr.com>,
John Kingman <kingman@storagegear.com>,
Peter Williams <pwil3058@bigpond.net.au>,
seuler.shi@gmail.com
Subject: Re: [RFC] Extend Linux to support proportional-share scheduling
Date: Wed, 6 Jun 2007 05:33:30 +0200 [thread overview]
Message-ID: <20070606033330.GB3266@1wt.eu> (raw)
In-Reply-To: <5FD5754DDBA0B1499B5A0B4BB54194850130685D@fmsmsx411.amr.corp.intel.com>
Hi Tong,
On Tue, Jun 05, 2007 at 06:56:17PM -0700, Li, Tong N wrote:
> Hi all,
>
> I've ported my code to mainline 2.6.21.3. You can get it at
> http://www.cs.duke.edu/~tongli/linux/.
as much as possible, you should post your patch for others to comment
on it. Posting just a URL is often fine to inform people that there's
an update to *try*, but at this stage, it may be more important to
comment on your design and code than trying it.
[...]
> Trio has two unique features: (1) it enables users to control shares of
> CPU time for any thread or group of threads (e.g., a process, an
> application, etc.), and (2) it enables fair sharing of CPU time across
> multiple CPUs. For example, with ten tasks running on eight CPUs, Trio
> allows each task to take an equal fraction of the total CPU time,
While this looks interesting, doesn't it make threads jump to random
CPUs all the time, thus reducing cache efficiency ? Or maybe it would
be good to consider two or three criteria to group CPUs :
- those which share the same caches (multi-core)
- those which share the same local memory on the same mainboard
(multi-socket)
- those which are so far away from each others that it's really
not worth migrating a task
> whereas no existing scheduler achieves such fairness. These features
> enable Trio to complement the mainline scheduler and other proposals
> such as CFS and SD to enable greater user flexibility and stronger
> fairness.
Right now, I think that only benchmarks could tell which design is
better. I understand that running 10 tasks on 8 CPUs may result in
the last batch involving only 2 CPUs with 1 task each, thus increasing
the overall wall time. But maybe cache thrashing between CPUs will
also increase the wall time.
Regards,
Willy
next prev parent reply other threads:[~2007-06-06 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 1:56 Li, Tong N
2007-06-06 3:33 ` Willy Tarreau [this message]
2007-06-06 4:31 ` Li, Tong N
2007-06-06 5:30 ` Willy Tarreau
2007-06-06 13:26 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2007-04-20 18:30 Tong Li
2007-04-21 4:24 ` William Lee Irwin III
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=20070606033330.GB3266@1wt.eu \
--to=w@1wt.eu \
--cc=arjan@infradead.org \
--cc=balbir@in.ibm.com \
--cc=billh@gnuppy.monkey.org \
--cc=davidsen@tmr.com \
--cc=jesse.barnes@intel.com \
--cc=kernel@kolivas.org \
--cc=kingman@storagegear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=seuler.shi@gmail.com \
--cc=suresh.b.siddha@intel.com \
--cc=tong.n.li@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vatsa@in.ibm.com \
--cc=wli@holomorphy.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®