From: Keika Kobayashi <kobayashi.kk@ncos.nec.co.jp>
To: dave@gnu.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RESEND] Fix /proc/softirqs file formatting
Date: Mon, 02 Aug 2010 08:51:55 +0900 [thread overview]
Message-ID: <4C56089B.9090405@ncos.nec.co.jp> (raw)
In-Reply-To: <1280516809.1955.0.camel@cowboy>
(2010/07/31 4:06), Davidlohr Bueso wrote:
> Hi,
>
> The length of the BLOCK_IPOLL string is making it's value be printed too
> far to the right. This patch fixes this and makes the output a bit
> neater.
>
> Currently:
> CPU0
> HI: 0
> TIMER: 599792
> NET_TX: 2
> NET_RX: 6
> BLOCK: 80807
> BLOCK_IOPOLL: 0
> TASKLET: 20012
> SCHED: 0
> HRTIMER: 63
> RCU: 619279
>
> With patch:
> CPU0
> HI: 0
> TIMER: 585582
> NET_TX: 2
> NET_RX: 6
> BLOCK: 80320
> BLOCK_IOPOLL: 0
> TASKLET: 19287
> SCHED: 0
> HRTIMER: 62
> RCU: 604441
>
>
>
> Thanks,
> Davidlohr
>
>
> Signed-off-by: Davidlohr Bueso <dave@gnu.org>
> ---
> fs/proc/softirqs.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/proc/softirqs.c b/fs/proc/softirqs.c
> index 1807c24..3799473 100644
> --- a/fs/proc/softirqs.c
> +++ b/fs/proc/softirqs.c
> @@ -10,13 +10,13 @@ static int show_softirqs(struct seq_file *p, void *v)
> {
> int i, j;
>
> - seq_printf(p, " ");
> + seq_printf(p, " ");
> for_each_possible_cpu(i)
> seq_printf(p, "CPU%-8d", i);
> seq_printf(p, "\n");
>
> for (i = 0; i < NR_SOFTIRQS; i++) {
> - seq_printf(p, "%8s:", softirq_to_name[i]);
> + seq_printf(p, "%12s:", softirq_to_name[i]);
> for_each_possible_cpu(j)
> seq_printf(p, " %10u", kstat_softirqs_cpu(i, j));
> seq_printf(p, "\n");
Sorry for late response.
It looks good to me.
// Keika Kobayashi
next prev parent reply other threads:[~2010-08-01 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 19:06 Davidlohr Bueso
2010-08-01 23:51 ` Keika Kobayashi [this message]
2010-08-06 14:52 ` Davidlohr Bueso
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=4C56089B.9090405@ncos.nec.co.jp \
--to=kobayashi.kk@ncos.nec.co.jp \
--cc=dave@gnu.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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®