From: Paul Jackson <pj@sgi.com>
To: "Bert Wesarg" <bert.wesarg@googlemail.com>
Cc: travis@sgi.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86: modify show_shared_cpu_map in intel_cacheinfo
Date: Mon, 31 Mar 2008 13:18:08 -0500 [thread overview]
Message-ID: <20080331131808.e21d494f.pj@sgi.com> (raw)
In-Reply-To: <36ca99e90803311024h6aeb89beyd72f73c3763c0a9c@mail.gmail.com>
Bert wrote:
> Sure your list is mostly shorter than a hex mask
"mostly" -- yup.
The masks always take 9 chars per 32 bits of the full mask size
(whether zeros or ones.)
The lists can take up to approx one to three chars per bit, for the
worst case lists of every other bit, depending on the log base 10 of
the highest included bit.
Consider for example:
97,99,101,103,105,107,109,111,113,115,117,119,121,123,125,127
vs.
AAAAAAAA,00000000,00000000,00000000
which, if I did my math right, are the same value.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-03-31 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 23:16 [PATCH 0/2] x86: add functions in preparation of cpumask changes Mike Travis
2008-03-27 23:16 ` [PATCH 1/2] x86: Convert cpumask_of_cpu macro to allocated array Mike Travis
2008-03-27 23:16 ` [PATCH 2/2] x86: modify show_shared_cpu_map in intel_cacheinfo Mike Travis
2008-03-28 9:01 ` Bert Wesarg
2008-03-28 14:40 ` Mike Travis
2008-03-28 14:54 ` Bert Wesarg
2008-03-28 18:19 ` Mike Travis
2008-03-29 8:59 ` Bert Wesarg
2008-03-31 16:35 ` Mike Travis
2008-03-31 17:24 ` Bert Wesarg
2008-03-31 18:18 ` Paul Jackson [this message]
2008-03-31 17:56 ` Paul Jackson
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=20080331131808.e21d494f.pj@sgi.com \
--to=pj@sgi.com \
--cc=bert.wesarg@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.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