From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: rusty@rustcorp.com.au (Rusty Russell),
anton@samba.org, davej@suse.de, marcelo@conectiva.com.br,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Linux 2.4.17-pre5
Date: 11 Dec 2001 02:00:23 -0700 [thread overview]
Message-ID: <m1ofl6uo60.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E16DEVr-0008SW-00@the-village.bc.nu>
In-Reply-To: <E16DEVr-0008SW-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > If you number each CPU so its two IDs are smp_num_cpus()/2
> > apart, you will NOT need to put some crappy hack in the
> > scheduler to pack your CPUs correctly.
>
> Which is a major change to the x86 tree and an invasive one. Right now the
> X86 is doing a 1:1 mapping, and I can offer Marcelo no proof that somewhere
> buried in the x86 arch code there isnt something that assumes this or mixes
> a logical and physical cpu id wrongly in error.
Actually we don't do a 1:1 physical to logical mapping. I currently
have a board that has physical id's of: 0:6 and logical id's of 0:1
with no changes to the current x86 code.
>
> At best you are exploiting an obscure quirk of the current scheduler that is
> quite likely to break the moment someone factors power management into the
> idling equation (turning cpus off and on is more expensive so if you idle
> a cpu you want to keep it the idle one for PM). Congratulations on your
> zen like mastery of the scheduler algorithm. Now tell me it wont change in
> that property.
The idea of a cpu priority for filling sounds like a nice one. Even
if we don't use the cpu id bits for it.
Eric
next prev parent reply other threads:[~2001-12-11 9:21 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 [this message]
2001-12-11 23:14 ` Alan Cox
2001-12-09 19:38 ` Marcelo Tosatti
2001-12-09 9:47 ` arjan
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=m1ofl6uo60.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rusty@rustcorp.com.au \
--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 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.