From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
kaneshige.kenji@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [RFC PATCH v2 1/5] irq: add tracepoint to softirq_raise
Date: Fri, 25 Jun 2010 10:10:44 +0900 (JST) [thread overview]
Message-ID: <20100625100718.8034.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <4C23FF0E.4020908@jp.fujitsu.com>
(cc to Lai)
> This patch adds a tracepoint to raising of softirq.
> This is useful if you want to detect which hard interrupt raise softirq
> and lets you know a time between raising softirq and performing softirq.
> Combinating with other tracepoint, it lets us know a process of packets
> (See patch 0/5).
>
> <idle>-0 [001] 241229.957184: softirq_raise: vec=3 [action=NET_RX]
> <idle>-0 [000] 241229.993399: softirq_raise: vec=1 [action=TIMER]
> <idle>-0 [000] 241229.993400: softirq_raise: vec=9 [action=RCU]
>
> This is a same patch Lai Jiangshan submitted.
> http://marc.info/?l=linux-kernel&m=126026122728732&w=2
If so, you shouldn't remove author's info. please fix the description
as following.
-------------------------------------------------------------------------
From: Lai Jiangshan <laijs@cn.fujitsu.com>
This patch adds a tracepoint to raising of softirq.
This is useful if you want to detect which hard interrupt raise softirq
and lets you know a time between raising softirq and performing softirq.
Combinating with other tracepoint, it lets us know a process of packets
(See patch 0/5).
<idle>-0 [001] 241229.957184: softirq_raise: vec=3 [action=NET_RX]
<idle>-0 [000] 241229.993399: softirq_raise: vec=1 [action=TIMER]
<idle>-0 [000] 241229.993400: softirq_raise: vec=9 [action=RCU]
This is a same below.
http://marc.info/?l=linux-kernel&m=126026122728732&w=2
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
--------------------------------------------------------------------------------
next prev parent reply other threads:[~2010-06-25 1:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C2312A8.9060903@jp.fujitsu.com>
2010-06-24 8:16 ` Koki Sanagi
2010-06-24 19:15 ` Steven Rostedt
2010-06-25 0:49 ` Koki Sanagi
2010-06-25 0:57 ` Koki Sanagi
2010-06-25 1:10 ` KOSAKI Motohiro [this message]
2010-06-25 7:46 ` Frederic Weisbecker
2010-06-25 7:51 ` Koki Sanagi
2010-06-25 0:58 ` [RFC PATCH v2 2/5] napi: convert trace_napi_poll to TRACE_EVENT Koki Sanagi
2010-06-25 1:11 ` KOSAKI Motohiro
2010-06-25 7:57 ` Frederic Weisbecker
2010-06-25 0:58 ` [RFC PATCH v2 3/5] netdev: add tracepoints to netdev layer Koki Sanagi
2010-06-28 18:09 ` Steven Rostedt
2010-06-29 0:27 ` Koki Sanagi
2010-06-25 0:59 ` [RFC PATCH v2 4/5] skb: add tracepoints to freeing skb Koki Sanagi
2010-06-25 4:55 ` Eric Dumazet
2010-06-25 7:12 ` Koki Sanagi
2010-06-25 20:05 ` Eric Dumazet
2010-06-28 0:25 ` Koki Sanagi
2010-06-28 18:12 ` Steven Rostedt
2010-06-29 0:28 ` Koki Sanagi
2010-06-25 0:59 ` [RFC PATCH v2 5/5] perf:add a script shows a process of packet Koki Sanagi
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=20100625100718.8034.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanagi.koki@jp.fujitsu.com \
/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
Powered by JetHome