From: William Lee Irwin III <wli@holomorphy.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: format_cpumask()
Date: Mon, 17 Nov 2003 15:35:42 -0800 [thread overview]
Message-ID: <20031117233542.GE22764@holomorphy.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F0F37B0@scsmsx401.sc.intel.com>
On Mon, Nov 17, 2003 at 10:49:31AM -0800, Luck, Tony wrote:
> That makes it had to write portable shell scripts (etc.) that can
> parse these values on both 32-bit and 64-bit systems? A bitmask with
> just cpu0 set looks like:
> 0000000100000000
> on a 32-bit machine. And like:
> 0000000000000001
> on a 64-bit machine. Heaven help the architectures (ia64, sparc, ppc)
> that support both 32-bit and 64-bit applications!
Okay, so we need to:
(a) zero-pad the 64-bit case
(b) pick a format the users actually like
I was trying to make it a NR_CPUS -bit integer with the highest nybbles
printed first. What's your favorite alternative?
-- wli
next prev parent reply other threads:[~2003-11-17 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 18:49 format_cpumask() Luck, Tony
2003-11-17 23:35 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 23:56 format_cpumask() Luck, Tony
2003-11-18 0:00 ` format_cpumask() William Lee Irwin III
2003-11-18 0:03 ` format_cpumask() William Lee Irwin III
[not found] ` <20031118002213.GA6272@tsunami.ccur.com>
2003-11-18 0:26 ` format_cpumask() William Lee Irwin III
2003-11-18 0:34 ` format_cpumask() Keith Owens
2003-11-18 0:56 ` format_cpumask() William Lee Irwin III
2003-11-17 3:35 format_cpumask() William Lee Irwin III
2003-11-19 9:32 ` format_cpumask() Paul Jackson
2003-11-19 10:38 ` format_cpumask() 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=20031117233542.GE22764@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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