From: Martin Hicks <mort@wildopensource.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org, wildos@sgi.com
Subject: Re: rename the ksoftirqd kernel thread.
Date: Fri, 16 May 2003 08:41:03 -0400 [thread overview]
Message-ID: <20030516124103.GB29266@bork.org> (raw)
In-Reply-To: <20030515215121.GC2669@werewolf.able.es>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Thu, May 15, 2003 at 11:51:21PM +0200, J.A. Magallon wrote:
>
> Standard Linux 2.4 only supports 32 CPUS (include/linux/threads.h).
> Wouldn't be useful to format it as %0.2d ?
> Even in -aa, that supports 64 in 64-bits arches, it would be enough and
> you get rid of the jump from _CPU9 to _CPU10.
I agree that currently there is only support for sizeof(long) CPUS.
Including this small fix will make the diff to run > 64 CPUS smaller
and will increase consistency between 2.4 and 2.5.
There are machines out there that are running 128 processors on 2.4
mh
--
Wild Open Source Inc. mort@wildopensource.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-05-16 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 21:17 rename the ksoftirqd kernel thread Martin Hicks
2003-05-15 21:51 ` J.A. Magallon
2003-05-16 12:41 ` Martin Hicks [this message]
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=20030516124103.GB29266@bork.org \
--to=mort@wildopensource.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=wildos@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