Re: [PATCH 1/3] Added new Proc entry to display per-cpu interrupts

[Thomas Gleixner]

On Tue, 17 Apr 2012, Sasikantha babu wrote:

Sigh. I told you before, that a subject line of a patch which starts
with: "Added ..." is useless.

Please use the proper prefix for the subsystem and a reasonable
subject.

> As the number of cores increases the output of the /proc/interrupts losing the readability.
> 

And please use a proper mail client which does line wraps around 78 chars.

> As the number of cores increases the output of the /proc/interrupts
> losing the readability.

That's how it should look like.

> I think instead of showing complete information of all cores in a
> single proc file spliting the information based on per-CPU will be
> more useful (especially for people who wants to track per-cpu
> information in real-time systems).

That has nothing to do with real time systems. /proc/interrupts is
unreadable on any machine with a large number of cores.

What the heck is wrong with

cat /proc/interrupts | grep $YOUR_IRQ_OF_INTEREST | awk '{ print $CPU_ROW }'


Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/