From: Thomas Gleixner <tglx@linutronix.de>
To: Sasikantha babu <sasikanth.v19@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Daniel Lezcano <daniel.lezcano@free.fr>,
Kevin Tian <kevin.tian@intel.com>,
Fengzhe Zhang <fengzhe.zhang@intel.com>,
Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Frysinger <vapier@gentoo.org>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 1/3] Added new Proc entry to display per-cpu interrupts
Date: Wed, 18 Apr 2012 00:56:53 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1204180034380.2542@ionos> (raw)
In-Reply-To: <1334677205-2623-1-git-send-email-sasikanth.v19@gmail.com>
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
prev parent reply other threads:[~2012-04-17 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 15:40 Sasikantha babu
2012-04-17 15:40 ` [PATCH 2/3] Added arch_show_interrupts_cpu to display CPU specific interrupts for Proc Fs Sasikantha babu
2012-04-17 15:40 ` [PATCH 3/3] Modified generic show_interrupts to display per-CPU interrupts information Sasikantha babu
2012-04-17 22:56 ` Thomas Gleixner [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=alpine.LFD.2.02.1204180034380.2542@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=daniel.lezcano@free.fr \
--cc=ebiederm@xmission.com \
--cc=fengzhe.zhang@intel.com \
--cc=fernando@oss.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sasikanth.v19@gmail.com \
--cc=vapier@gentoo.org \
--cc=x86@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
all inboxes | Powered by JetHome®