From: James Bottomley <James.Bottomley@steeleye.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH][2.5] fix for_each_cpu compilation on UP
Date: Fri, 17 Jan 2003 10:03:55 -0500 [thread overview]
Message-ID: <200301171503.h0HF3vr02010@localhost.localdomain> (raw)
In-Reply-To: Message from Zwane Mwaikambo <zwane@holomorphy.com> of "Fri, 17 Jan 2003 00:01:10 EST." <Pine.LNX.4.44.0301162358060.24250-100000@montezuma.mastecende.com>
zwane@holomorphy.com said:
> This adds a definition for for_each_cpu when !CONFIG_SMP
> Please apply
Could you elaborate on the purpose of this a bit? for_each_cpu() is only used
by the voyager subarch on x86 to traverse sparse CPU bitmaps efficiently in
critical path code. It has no other use in x86 SMP because all other
subarch's tend to compact the CPU bitmap much more.
If there are other uses for the construct, it should probably be put in bitops
and become for_each_bit(i, mask)
James
next prev parent reply other threads:[~2003-01-17 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 5:01 Zwane Mwaikambo
2003-01-17 5:54 ` Andrew Morton
2003-01-17 15:03 ` James Bottomley [this message]
2003-01-17 16:44 ` Zwane Mwaikambo
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=200301171503.h0HF3vr02010@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@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
all inboxes | Powered by JetHome®