From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: davidm@hpl.hp.com
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, "" <alan@lxorguk.ukuu.org.uk>,
"" <akpm@zip.com.au>, "" <linux-kernel@vger.kernel.org>
Subject: Re: proc_misc.c bug
Date: Fri, 11 Apr 2003 01:46:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.50.0304110145070.540-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <16022.21891.554860.506152@napali.hpl.hp.com>
On Thu, 10 Apr 2003, David Mosberger wrote:
> Wouldn't the kmalloc() likely fail in fragmented conditions? Also,
> I'm wondering whether there is such a thing as "well-tuned" in this
> case. For example, in the extreme case of the SGI SN2 machine, each
> CPU could in theory have up to 256 interrupt sources (OK, perhaps it's
> only 256 interrupts per 2 CPUs, but it's still a lot of interrupts to
> go around ;-). OTOH, most ia64 machines out there have less than 256
> interrupt per _system_. That's a large variation.
I think NR_CPUS belongs in there somewhere, this is what triggered the
original change;
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12 CPU13 CPU14 CPU15 CPU16 CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 CPU24 CPU25 CPU26 CPU27 CPU28 CPU29 CPU30 CPU31
0: 3652909 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 local-APIC-edge timer
2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 XT-PIC cascade
4: 2274 2134 1993 2147 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-edge serial
8: 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level rtc
19: 1082 1068 527 1118 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth0
37: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth7
38: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth6
39: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth5
40: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth4
41: 3558 2894 2648 3244 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level qlogicisp
89: 0 0 0 0 4 4 4 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level qlogicisp
115: 0 0 0 0 0 0 0 0 361 366 366 347 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth1
163: 0 0 0 0 0 0 0 0 0 0 0 0 383 385 385 384 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth2
211: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 375 376 374 375 0 0 0 0 0 0 0 0 0 0 0 0 IO-APIC-level eth3
NMI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
LOC: 3604478 3603640 3603819 3603799 3603663 3603641 3603627 3603601 3603603 3603583 3603563 3603542 3603588 3603567 3603546 3603526 3603416 3603394 3603374 3603352 3603601 3603578 3603557 3603536 3603707 3603686 3603665 3603644 3603430 3603410 3603388 3603368
ERR: 0
MIS: 0
--
function.linuxpower.ca
next prev parent reply other threads:[~2003-04-11 5:42 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-10 22:02 proc_misc.c bug David Mosberger 2003-04-10 21:44 ` Alan Cox 2003-04-10 22:49 ` Randy.Dunlap 2003-04-11 5:01 ` Randy.Dunlap 2003-04-11 5:28 ` Andrew Morton 2003-04-11 5:41 ` David Mosberger 2003-04-11 5:46 ` Zwane Mwaikambo [this message] 2003-04-11 17:29 ` Randy.Dunlap 2003-04-11 18:32 ` David Mosberger 2003-04-10 22:53 ` Andrew Morton 2003-04-11 0:27 ` David Mosberger 2003-04-10 22:18 ` Andrew Morton
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=Pine.LNX.4.50.0304110145070.540-100000@montezuma.mastecende.com \
--to=zwane@linuxpower.ca \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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; as well as URLs for NNTP newsgroup(s).