From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: kobayashi.kk@ncos.nec.co.jp
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, h-shimamoto@ct.jp.nec.com
Subject: Re: [PATCH 2/3 v2] proc: Export statistics for softirq to /proc
Date: Sun, 11 Jan 2009 04:44:38 +0900 [thread overview]
Message-ID: <2f11576a0901101144y66c072e9w5da6bde9d000e907@mail.gmail.com> (raw)
In-Reply-To: <51c5bc110901101022g1fc407f6ifc37aa93580a2da1@mail.gmail.com>
>>> You can calcurate per_irq_sum here.
>>> Typically, # of possible cpu are very big.
>>>
>>> So, I don't like unnecessary twrice looping.
>>
>> I was about to send these patches to Linus, but it seems that this
>> optmisation hasn't been addressed?
>
> Thanks for your notice, Andrew.
> Of course, thanks for your advice, Kosaki-san.
> I didn't check carefully about this point...
>
> Now I am on a business trip.
> So, I'll post the fix next week.
No problem.
I've made it three hour ago. I'll post soon.
next prev parent reply other threads:[~2009-01-10 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 4:22 [PATCH 0/3 v2] softirq: Statistics for softirq Keika Kobayashi
2008-11-22 4:25 ` [PATCH 1/3 v2] softirq: Introduce statistics " Keika Kobayashi
2008-11-22 5:36 ` KOSAKI Motohiro
2008-11-24 23:46 ` Keika Kobayashi
2008-11-26 10:14 ` KOSAKI Motohiro
2008-11-22 4:27 ` [PATCH 2/3 v2] proc: Export statistics for softirq to /proc Keika Kobayashi
2008-11-22 11:36 ` Eric Dumazet
2008-11-26 10:10 ` KOSAKI Motohiro
2009-01-09 22:16 ` Andrew Morton
2009-01-10 18:22 ` kobayashi.kk
2009-01-10 19:44 ` KOSAKI Motohiro [this message]
2009-01-12 11:46 ` KOSAKI Motohiro
2009-01-12 23:53 ` kobayashi.kk
2008-11-22 4:28 ` [PATCH 3/3 v2] proc: Update document for /proc/softirqs and /proc/stat Keika Kobayashi
2008-11-26 10:11 ` KOSAKI Motohiro
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=2f11576a0901101144y66c072e9w5da6bde9d000e907@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=kobayashi.kk@ncos.nec.co.jp \
--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®