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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 18 Apr 2012 00:56:53 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Sasikantha babu <sasikanth.v19@...il.com>
cc:	Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Daniel Lezcano <daniel.lezcano@...e.fr>,
	Kevin Tian <kevin.tian@...el.com>,
	Fengzhe Zhang <fengzhe.zhang@...el.com>,
	Fernando Luis Vazquez Cao <fernando@....ntt.co.jp>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Marc Zyngier <marc.zyngier@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mike Frysinger <vapier@...too.org>,
	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH 1/3] Added new Proc entry to display per-cpu interrupts

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/