linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Paul Jackson <pj@sgi.com>
Cc: linux-kernel@vger.kernel.org, anton@samba.org, ak@muc.de
Subject: Re: format_cpumask()
Date: Wed, 19 Nov 2003 02:38:15 -0800	[thread overview]
Message-ID: <20031119103815.GE19856@holomorphy.com> (raw)
In-Reply-To: <20031119013238.21944da9.pj@sgi.com>

On Wed, Nov 19, 2003 at 01:32:38AM -0800, Paul Jackson wrote:
> Wouldn't it be a good idea to pass in the length of the remaining
> available buffer space and use snprintf, to avoid overruns?
> We're going to end up with some pretty big cpumasks on some systems --
> running over a buffer would be nasty.  It would mostly happen during
> bring up of new bigger systems; but still worth avoiding.
> A second thought - more controversial - long sequences of digits can get
> pretty difficult to read.  How about breaking them with a separator
> character, say every 32 or 64 bits.

I'm happy just to get the numbers into _some_ format that makes sense.
This could very well be an improvement over the large hexadecimal
number. I say run with it.


-- wli

  reply	other threads:[~2003-11-19 10:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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   ` William Lee Irwin III [this message]
2003-11-17 18:49 format_cpumask() Luck, Tony
2003-11-17 23:35 ` format_cpumask() William Lee Irwin III
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

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=20031119103815.GE19856@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=ak@muc.de \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@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;
as well as URLs for NNTP newsgroup(s).