public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpu-2.5.64-1
Date: Sun, 16 Mar 2003 22:53:19 +1100	[thread overview]
Message-ID: <17605.1047815599@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 16 Mar 2003 03:32:54 -0800." <20030316113254.GH20188@holomorphy.com>

On Sun, 16 Mar 2003 03:32:54 -0800, 
William Lee Irwin III <wli@holomorphy.com> wrote:
>On Sun, Mar 16, 2003 at 10:12:24PM +1100, Keith Owens wrote:
>> Some of the 64 bit archs implement test_bit() as taking int * instead
>> of long *.  That generates unoptimized code for the case of NR_CPUS <
>> 64.

Come to think of it, using any of the bitops generates unoptimized code
for cpu mask testing when we know that NR_CPUS will fit into a single
long.  For NR_CPUS <= 8*sizeof(long), using mask & (1UL << cpu) removes
the unnecessary array calculations.

>What's the state of 2.5.x on the big machines where you're at?

I could tell you, but then marketing would kill me :(  Wait a bit.

>Another thought I had was wrapping things in structures for both small
>and large, even UP systems so proper typechecking is enforced at all
>times. That would probably need a great deal of arch sweeping to do,
>especially as a number of arches are UP-only (non-SMP case's motive #2).

Keep the optimized model, where cpu_online_map is #defined to 1 for UP.
Changing it to an ADT just to get type checking on architectures that
only support UP looks like a bad tradeoff.


  reply	other threads:[~2003-03-16 11:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  4:24 cpu-2.5.64-1 William Lee Irwin III
2003-03-11  7:17 ` cpu-2.5.64-1 Zwane Mwaikambo
2003-03-11  8:25   ` cpu-2.5.64-1 Zwane Mwaikambo
2003-03-16  7:39 ` cpu-2.5.64-1 Keith Owens
2003-03-16  8:36   ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16  9:19     ` cpu-2.5.64-1 Keith Owens
2003-03-16  9:46       ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 10:10       ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 11:12         ` cpu-2.5.64-1 Keith Owens
2003-03-16 11:32           ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 11:53             ` Keith Owens [this message]
2003-03-16 12:00               ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 12:42             ` cpu-2.5.64-1 Horst von Brand
2003-03-16 19:14               ` cpu-2.5.64-1 William Lee Irwin III

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=17605.1047815599@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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