From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Theurer <habanero@us.ibm.com>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4.19-rc3 (hyperthreading)
Date: Tue, 30 Jul 2002 02:04:28 +0200 [thread overview]
Message-ID: <20020730000428.GN1201@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44L.0207292051040.3086-100000@imladris.surriel.com>
On Mon, Jul 29, 2002 at 08:51:51PM -0300, Rik van Riel wrote:
> On Tue, 30 Jul 2002, Andrea Arcangeli wrote:
>
> > and the new one had a bug too :). Please merge the fix I posted to l-k
> > too thanks.
>
> Judging from the patch the code seems incredibly subtle and
> I'd be amazed if it doesn't break again every few weeks...
what's subtle exactly? I found the SD_MAJOR >>4, << 8 >> 8 16 devnum <<
4 in sd.c subtle, this doesn't look subtle to me. The code simply avoids
to rebalance the current idle cpu if the sibling isn't idle too and it
tries to idle reschedule another idle package (with both sibling idle)
instead. The coding is in coherent style with the rest of the o1
scheduler as far I can tell.
Andrea
next prev parent reply other threads:[~2002-07-30 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 19:54 Linux 2.4.19-rc3 (hyperthreading) Andrew Theurer
2002-07-29 21:28 ` Alan Cox
2002-07-29 20:38 ` Andrea Arcangeli
2002-07-29 23:45 ` Andrea Arcangeli
2002-07-29 23:51 ` Rik van Riel
2002-07-30 0:04 ` Andrea Arcangeli [this message]
2002-07-30 0:09 ` J.A. Magallon
2002-07-30 0:32 ` Andrea Arcangeli
2002-07-31 3:08 ` Bill Davidsen
2002-07-31 12:43 ` Rik van Riel
2002-07-31 14:16 ` Sam Vilain
2002-08-01 18:29 ` Ingo Oeser
2002-07-29 20:58 ` Andrew Theurer
2002-07-30 0:37 ` Alan Cox
2002-07-29 23:42 ` Andrew Theurer
2002-07-30 0:56 ` James Bourne
2002-07-30 0:47 ` James Bourne
2002-07-30 1:15 ` Andrew Theurer
2002-07-30 3:09 ` James Bourne
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=20020730000428.GN1201@dualathlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=habanero@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).