From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] show_mem() printk levels
Date: Thu, 21 Sep 2006 12:40:37 +0000 [thread overview]
Message-ID: <45128845.4050201@sgi.com> (raw)
In-Reply-To: <yq04pvcey2p.fsf@jaguar.mkp.net>
Christoph Lameter wrote:
> On Thu, 14 Sep 2006, Jes Sorensen wrote:
>
>> Actually it's far worse than that if I got the math right, it will
>> print in the order of 2 * NR_CPUS * NR_NODES * nr_zones, which for a
>> machine with 1024 cpus and 1024 nodes will result in 2 million lines
>> plus a bit of other noise.
>>
>> This is a problem on all architectures, not just ia64, so I have a
>> patch to try and trim that down too, so it gets done right. But we may
>> also want to consider dropping the call altogether for ia64 or maybe
>> if the number of nodes is larger than a certain amount (but I don't
>> like inconsistent behavior depending on the size of a system).
>
> Please lets just drop the call for ia64. For systems with a few cpus
> (typical for Linux use) the diagnostics are very useful.
I'm fine with this - anybody objecting to this call being dropped for
ia64? We could do something where we only call it if the number of nodes
is lower than a certain threshold, but IMHO it's better to be
consistent?
Comments,
Jes
prev parent reply other threads:[~2006-09-21 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 12:43 [patch] show_mem() printk levels Jes Sorensen
2006-09-13 17:28 ` Christoph Lameter
2006-09-14 8:27 ` Jes Sorensen
2006-09-14 16:47 ` Christoph Lameter
2006-09-21 12:40 ` Jes Sorensen [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=45128845.4050201@sgi.com \
--to=jes@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