pcp
[Top] [All Lists]

Re: [pcp] proc/interrupts parsing fix for large CPU counts

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] proc/interrupts parsing fix for large CPU counts
From: Mark Goodwin <goodwinos@xxxxxxxxx>
Date: Thu, 27 Jan 2011 15:34:44 +1100
In-reply-to: <1296082087.18982.14.camel@xxxxxxxxxxxxxxxx>
References: <20110126213328.GB10691@xxxxxxx> <1296082087.18982.14.camel@xxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Thunderbird/3.1.6
On 01/27/2011 09:48 AM, Ken McDonell wrote:
Thanks Arthur ... I'll commit this patch.

But, can some who's familiar with the code in this area please cast an
eye over the proc_interrupts->syscall[cpu] and is_syscall code in this
same source file.

a) the is_syscall logic does not seem right compared to
the /proc/interrupts contents on my local system, and

b) proc_interrupts->syscall[cpu] is set but never returned in a
fetch ... which is why the apparent error in a) has not been noticed?

These oddities are independent of the other interrupts metrics that
Arthur's patch accommodates.


I'm not 100% sure, but I think the "SYS" entries in /proc/interrupts
might have been something I added to SGI only kernels many years
ago. This was an SGI-only patch for per-cpu system call counters.
(IIRC, the patch was never posted because it needed changes on every
arch).

Nathan and I just checked a few kernels, including as far back as
the RHEL4 2.6.9 kernel and there's no sign of any SYS entries in
/proc/interrupts, so unless someone else pipes up, I think this is
probably dead code and we can nuke it.

Cheers
-- Mark

<Prev in Thread] Current Thread [Next in Thread>