From: arjan@fenrus.demon.nl
To: rusty@rustcorp.com.au (Rusty Russell)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.17-pre5
Date: Sun, 9 Dec 2001 09:47:46 +0000 (GMT) [thread overview]
Message-ID: <m16D0Yk-000OXEC@amadeus.home.nl> (raw)
In-Reply-To: <20011208214631.75573e9a.rusty@rustcorp.com.au>
In article <20011208214631.75573e9a.rusty@rustcorp.com.au> you wrote:
> On Fri, 7 Dec 2001 00:09:12 +0000 (GMT)
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> > > Actually that one is various Intel people not me 8)
>> >
>> > Wouldn't it be better to see such things proven right in 2.5 first ?
>>
>> o 2.5 isnt going to be usable for that kind of thing in the near future
>> o There is no code that is "new" for normal paths (in fact Marcelo
>> wanted a change for the only "definitely harmless" one there was)
> The sched.c change is also useless (ie. only harmful).
The intention seems to be to avoid the situation where one "pair" is
executing 2 processes while other "pair"s are fully idle. It makes a
difference for the "system is < 50% busy" case, NOT for the "system is very
busy" case....
next prev parent reply other threads:[~2001-12-09 9:48 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 17:39 Linux 2.4.17-pre5 Marcelo Tosatti
2001-12-06 19:07 ` Alan Cox
2001-12-06 23:38 ` Dave Jones
2001-12-07 0:09 ` Alan Cox
2001-12-08 10:46 ` Rusty Russell
2001-12-09 0:17 ` Linux HMT analysis Anton Blanchard
2001-12-09 1:39 ` Alan Cox
2001-12-09 1:41 ` Alan Cox
2001-12-09 0:31 ` Linux 2.4.17-pre5 Alan Cox
2001-12-09 1:58 ` Rusty Russell
2001-12-09 2:35 ` Davide Libenzi
2001-12-09 6:20 ` Rusty Russell
2001-12-09 16:24 ` Alan Cox
2001-12-09 19:48 ` Davide Libenzi
2001-12-09 22:44 ` Mike Kravetz
2001-12-09 23:50 ` Davide Libenzi
2001-12-09 23:57 ` Alan Cox
2001-12-19 22:16 ` Pavel Machek
2001-12-20 19:10 ` Davide Libenzi
2001-12-09 16:16 ` Alan Cox
2001-12-10 0:21 ` Rusty Russell
2001-12-10 0:41 ` Alan Cox
2001-12-10 2:10 ` Martin J. Bligh
2001-12-10 5:40 ` Rusty Russell
2001-12-10 5:31 ` Rusty Russell
2001-12-10 8:28 ` Alan Cox
2001-12-10 23:12 ` James Cleverdon
2001-12-10 23:30 ` Alan Cox
2001-12-11 9:16 ` Robert Varga
2001-12-11 9:23 ` David Weinehall
2001-12-11 9:00 ` Eric W. Biederman
2001-12-11 23:14 ` Alan Cox
2001-12-09 19:38 ` Marcelo Tosatti
2001-12-09 9:47 ` arjan [this message]
2001-12-07 16:07 ` Marcelo Tosatti
2001-12-06 19:18 ` Matthias Andree
2001-12-06 19:05 ` Marcelo Tosatti
2001-12-06 21:14 ` Ben Greear
2001-12-06 21:58 ` David S. Miller
2001-12-06 22:24 ` Matthias Andree
2001-12-09 10:10 ` Eran Man
2001-12-06 20:14 ` Rik van Riel
2001-12-06 20:22 ` Jeff Garzik
2001-12-06 20:58 ` David S. Miller
2001-12-08 4:56 ` M. Edward Borasky
2001-12-08 5:41 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 20:44 Luca Montecchiani
2001-12-07 0:12 ` Stephan von Krawczynski
2001-12-07 3:43 ` Keith Owens
2001-12-07 11:55 ` Stephan von Krawczynski
2001-12-07 13:35 ` Keith Owens
2001-12-07 14:25 ` Stephan von Krawczynski
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=m16D0Yk-000OXEC@amadeus.home.nl \
--to=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.