From: Rusty Russell <rusty@rustcorp.com.au>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: timothy.covell@ashavan.org,
"François Cami" <stilgar2k@wanadoo.fr>,
"Ingo Molnar" <mingo@elte.hu>,
"Mike Kravetz" <kravetz@us.ibm.com>,
"Linus Torvalds" <torvalds@transmeta.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Anton Blanchard" <anton@samba.org>,
"george anzinger" <george@mvista.com>,
"Rusty Russell" <rusty@rustcorp.com.au>
Subject: Re: [patch] O(1) scheduler, -G1, 2.5.2-pre10, 2.4.17 (fwd)
Date: Sun, 13 Jan 2002 17:59:33 +1100 [thread overview]
Message-ID: <E16Pec9-0004jY-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Sat, 12 Jan 2002 12:44:30 -0800." <Pine.LNX.4.40.0201121237110.1559-100000@blue1.dev.mcafeelabs.com>
In message <Pine.LNX.4.40.0201121237110.1559-100000@blue1.dev.mcafeelabs.com> y
ou write:
> > Aside from the cache utilization, this is not really "fair" -- the
> > problem is, the current design of load_balance (which is quite good)
> > just won't throw the tasks around so readily. What could be done --
> > cleanly -- to make this better?
>
> My opinion is: if it can be solved with no more than 20 lines of code
> let's do it, otherwise let's see what kind of catastrophe will happen by
> allowing such behavior.
Agree. Anyone who really has 3 CPU hogs on a 2 CPU machine, *and*
never runs two more tasks to perturb the system, *and* notices that
one runs twice the speed of the other two, *and* cares about fairness
(ie. not RC5 etc), feel free to Email abuse to me. Not Ingo, he has
real work to do 8)
Cheers!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-01-13 6:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 14:19 Ingo Molnar
2002-01-10 18:20 ` Linus Torvalds
2002-01-10 20:11 ` george anzinger
2002-01-10 23:54 ` Ingo Molnar
2002-01-10 23:22 ` Ingo Molnar
2002-01-11 0:01 ` Ingo Molnar
2002-01-10 20:01 ` Robert Love
2002-01-10 23:44 ` Ingo Molnar
2002-01-10 21:57 ` Mike Kravetz
2002-01-11 0:48 ` Ingo Molnar
2002-01-10 23:04 ` Davide Libenzi
2002-01-11 21:42 ` François Cami
2002-01-11 21:46 ` Timothy Covell
[not found] ` <1010814327.2018.5.camel@phantasy>
2002-01-12 11:48 ` François Cami
2002-01-12 16:26 ` Timothy Covell
2002-01-12 20:00 ` Robert Love
2002-01-12 20:44 ` Davide Libenzi
2002-01-12 20:44 ` Timothy Covell
2002-01-12 23:56 ` Robert Love
2002-01-13 6:59 ` Rusty Russell [this message]
2002-01-14 8:40 ` Marian Jancar
2002-01-11 21:53 ` Mark Hahn
2002-01-13 20:30 Dieter Nützel
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=E16Pec9-0004jY-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=anton@samba.org \
--cc=davidel@xmailserver.org \
--cc=george@mvista.com \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stilgar2k@wanadoo.fr \
--cc=timothy.covell@ashavan.org \
--cc=torvalds@transmeta.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
Powered by JetHome