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 16:00:21 -0800 [thread overview]
Message-ID: <20031118000021.GF22764@holomorphy.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F0F37B8@scsmsx401.sc.intel.com>
At some point in the past, I wrote:
>> I was trying to make it a NR_CPUS -bit integer with the
>> highest nybbles
>> printed first. What's your favorite alternative?
On Mon, Nov 17, 2003 at 03:56:34PM -0800, Luck, Tony wrote:
> 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
This is actually what I was trying to do. It's why I started the
loop of printing out the hexadecimal unsigned long components with
for (k = sizeof(cpumask_t)/sizeof(long) - 1; k >= 0; --k);
except I posted ++k. Amended patch coming very shortly.
-- wli
next prev parent reply other threads:[~2003-11-18 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 23:56 format_cpumask() Luck, Tony
2003-11-18 0:00 ` William Lee Irwin III [this message]
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=20031118000021.GF22764@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 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.