From: William Lee Irwin III <wli@holomorphy.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpu-2.5.64-1
Date: Sun, 16 Mar 2003 04:00:57 -0800 [thread overview]
Message-ID: <20030316120057.GI20188@holomorphy.com> (raw)
In-Reply-To: <17605.1047815599@ocs3.intra.ocs.com.au>
On Sun, 16 Mar 2003 03:32:54 -0800, William Lee Irwin III wrote:
>> 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).
On Sun, Mar 16, 2003 at 10:53:19PM +1100, Keith Owens wrote:
> 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.
It shouldn't hurt UP:
typedef { unsigned long mask; } cpumask_t;
#define cpu_online_map ({ 1UL })
or some such nonsense with all the usual special cases. The arch code
impact OTOH can't really be gotten around with such tricks, if it's
significant. More food for thought...
-- wli
next prev parent reply other threads:[~2003-03-16 11:50 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 ` cpu-2.5.64-1 Keith Owens
2003-03-16 12:00 ` William Lee Irwin III [this message]
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=20030316120057.GI20188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/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.