From: Paul Jackson <pj@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - prof_cpu_mask problems
Date: Thu, 20 Nov 2003 02:17:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106929475727936@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106901123527791@msgid-missing>
> It was to silence a warning.
ah - ok - thanks.
> You'll have write your own to replace
> the fix now in -mm if this is what you really want.
I'm doing that now; and un-duplicating about a dozen instances of the
binary->string conversion loops used when reading out masks, and almost
as many string->binary parse_hex_value() routines used when reading in
masks. There will be a single routine for each, in a new lib file.
Can you tell me, Bill, how it is that having:
#define HEX_DIGITS (2*sizeof(cpumask_t))
leaves room for the terminating nul-byte? Seems to me that
a lot of hexnum[] arrays might be one byte short.
One incompatibility with existing code:
If I proceed along my current path, cpumasks, such as for
irq or smp_affinity, will no longer be displayed in /proc
with leading zero padding.
I expect that this could be a problem ...
Complaints invited.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2003-11-20 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 19:30 [PATCH] - prof_cpu_mask problems Jack Steiner
2003-11-16 21:25 ` Matthew Wilcox
2003-11-17 17:16 ` Luck, Tony
2003-11-17 17:30 ` Matthew Wilcox
2003-11-19 21:45 ` Paul Jackson
2003-11-19 22:54 ` William Lee Irwin III
2003-11-20 2:17 ` Paul Jackson [this message]
2003-11-20 2:38 ` Paul Jackson
2003-11-20 2:47 ` William Lee Irwin III
2003-11-20 2:59 ` Paul Jackson
2003-11-20 4:47 ` 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=marc-linux-ia64-106929475727936@msgid-missing \
--to=pj@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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