From: William Lee Irwin III <wli@holomorphy.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [cpumask_t 1/3] core changes for 2.5.67-bk6
Date: Fri, 18 Apr 2003 10:51:38 -0700 [thread overview]
Message-ID: <20030418175138.GA12469@holomorphy.com> (raw)
In-Reply-To: <20030418102015.2527ff40.rddunlap@osdl.org>
On Tue, 15 Apr 2003 15:50:36 -0700 William Lee Irwin III wrote:
> | Core changes for extended cpu masks. Basically use a machine word
> | #if NR_CPUS < BITS_PER_LONG, otherwise, use a structure with an array
> | of unsigned longs for it. Sprinkle it around the scheduler and a few
> | other odd places that play with the cpu bitmasks. Back-ended by a
> | bitmap ADT capable of dealing with arbitrary-width bitmaps, with the
> | obvious micro-optimizations for NR_CPUS < BITS_PER_LONG and UP.
> | NR_CPUS % BITS_PER_LONG != 0 is invalid while NR_CPUS > BITS_PER_LONG.
On Fri, Apr 18, 2003 at 10:20:15AM -0700, Randy.Dunlap wrote:
> Where/why this restriction (above)?
> I don't see the need for it or implementation of it.
> I'm only looking at the core patch.
I leave bits dangling otherwise.
On Tue, 15 Apr 2003 15:50:36 -0700 William Lee Irwin III wrote:
> | +static inline void bitmap_shift_left(volatile unsigned long *,volatile unsigned long *,int,int);
On Fri, Apr 18, 2003 at 10:20:15AM -0700, Randy.Dunlap wrote:
> Do you need this prototype? I don't see why.
> Rest of core looks good to me.
Probably not. I'll nuke it.
-- wli
prev parent reply other threads:[~2003-04-18 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:50 [cpumask_t 1/3] core changes for 2.5.67-bk6 William Lee Irwin III
2003-04-15 22:58 ` [cpumask_t 2/3] i386 " William Lee Irwin III
2003-04-15 23:08 ` [cpumask_t 3/3] ia64 " William Lee Irwin III
2003-04-18 17:20 ` [cpumask_t 1/3] core " Randy.Dunlap
2003-04-18 17:51 ` William Lee Irwin III [this message]
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=20030418175138.GA12469@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox