From: Robert Love <rml@tech9.net>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, Dave Jones <davej@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] scheduler bits from 2.5.23-dj1
Date: 19 Jun 2002 17:10:52 -0700 [thread overview]
Message-ID: <1024531852.917.29.camel@sinai> (raw)
In-Reply-To: <20020620000751.GI22262@dualathlon.random>
On Wed, 2002-06-19 at 17:07, Andrea Arcangeli wrote:
> obviously not. Supporting 4G cpus is enough for this century, so the
> other 32bit would be just wasted space. the 1 in the shiftleft needs the
> UL anyways to be correct with >32 cpus (it's not strictly a bug right
> now to forget the UL but if we get it right we'll be able to go 64-way
> on 64bit systems with no change other than NR_TASKS). So the bitmasks
> must be all unsigned longs, the cpu numbers are definitely fine as
> unsigned ints.
Eh, very true. I was confusing the bitmasks and the counts.
Sorry, Ingo - ignore me.
Robert Love
next prev parent reply other threads:[~2002-06-20 0:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 11:23 Linux 2.5.23-dj1 Dave Jones
2002-06-19 23:36 ` [patch] scheduler bits from 2.5.23-dj1 Ingo Molnar
2002-06-19 23:47 ` Robert Love
2002-06-20 0:07 ` Andrea Arcangeli
2002-06-20 0:10 ` Robert Love [this message]
2002-06-19 23:47 ` Dave Jones
2002-06-20 17:20 ` William Lee Irwin III
2002-06-20 17:31 ` Ingo Molnar
2002-06-20 17:52 ` William Lee Irwin III
2002-06-20 18:17 ` William Lee Irwin III
2002-06-20 19:26 ` William Lee Irwin III
2002-06-21 1:34 ` William Lee Irwin III
2002-06-19 23:56 ` William Lee Irwin III
2002-06-20 7:26 ` Manik Raina
2002-06-20 13:13 ` Ingo Molnar
2002-06-20 13:34 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 10:11 Mikael Pettersson
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=1024531852.917.29.camel@sinai \
--to=rml@tech9.net \
--cc=James.Bottomley@SteelEye.com \
--cc=andrea@suse.de \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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