From: Paul Jackson <pj@sgi.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, ioe-lkml@rameria.de,
shemminger@osdl.org, sylvain.jeaugey@bull.net, raybry@sgi.com,
hch@infradead.org, Simon.Derr@bull.net, wli@holomorphy.com
Subject: Re: [PATCH] another minor bit of cpumask cleanup
Date: Tue, 23 Dec 2003 19:18:35 -0800 [thread overview]
Message-ID: <20031223191835.26c974f2.pj@sgi.com> (raw)
In-Reply-To: <20031224023632.5D5462C260@lists.samba.org>
> thanks for reviewing!
My pleasure.
> Maybe Dave will be convinced: he's dogmatic, but rarely unreasonable.
On the third hand, it would be unreasonable of me to expect Dave to
agree to shoot his products performance in the foot for the sake of my
"more refined" coding style sensibilities.
> I think we'll only be able to tell with the patch in front of us.
I could publish an early version of it now, but I am supposed to be
on vacation now with my family, so should avoid starting a discussion
that I shouldn't participate in.
> Someday someone will enable VOYAGER_DEBUG and they'll fix it.
yup
> In 2.7, my aim is to switch the rest of them, move more things to
> per-cpu rather than [NR_CPUS] arrays, add the more efficient dynamic
> per-cpu allocation, and spread the per-cpu religion by fire and the
> sword.
For folks doing really large cpu counts, like my employer, this might
become of interest sooner. On the other hand, we do really large memory
as well, so this might not be especially critical to us.
If NR_CPUS arrays start to annoy us sooner, I'll know where to consult.
--
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-12-24 3:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 2:00 [PATCH] another minor bit of cpumask cleanup Paul Jackson
2003-12-22 2:14 ` William Lee Irwin III
2003-12-22 6:47 ` Andrew Morton
2003-12-22 7:19 ` Paul Jackson
2003-12-22 8:57 ` William Lee Irwin III
2003-12-22 12:32 ` Paul Jackson
2003-12-23 1:45 ` Rusty Russell
2003-12-23 10:10 ` Paul Jackson
2003-12-24 1:26 ` Rusty Russell
2003-12-24 3:18 ` Paul Jackson [this message]
2003-12-24 10:55 ` 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=20031223191835.26c974f2.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=raybry@sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@osdl.org \
--cc=sylvain.jeaugey@bull.net \
--cc=wli@holomorphy.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