From: "Luck, Tony" <tony.luck@intel.com>
To: "William Lee Irwin III" <wli@holomorphy.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: format_cpumask()
Date: Mon, 17 Nov 2003 15:56:34 -0800 [thread overview]
Message-ID: <B8E391BBE9FE384DAA4C5C003888BE6F0F37B8@scsmsx401.sc.intel.com> (raw)
> I was trying to make it a NR_CPUS -bit integer with the
> highest nybbles
> printed first. What's your favorite alternative?
The prettiest output format I can think of would be
to pretend that we had enough bits for NR_CPUS. I.e.
on a 128 cpu system, cpu0 looks like:
00000000000000000000000000000001
and cpu 127 is:
80000000000000000000000000000000
This is probably the messiest to implement :-(
-Tony
next reply other threads:[~2003-11-17 23:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 23:56 Luck, Tony [this message]
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-28 20:54 ` [PATCH] new /proc/irq cpumask format; consolidate cpumask display and input code Paul Jackson
2003-11-28 21:09 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 18:49 format_cpumask() Luck, Tony
2003-11-17 23:35 ` 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=B8E391BBE9FE384DAA4C5C003888BE6F0F37B8@scsmsx401.sc.intel.com \
--to=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).