public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	izumi.taku@jp.fujitsu.com, kaneshige.kenji@jp.fujitsu.com,
	acme@ghostprotocols.net, fweisbec@gmail.com, mingo@elte.hu,
	rostedt@goodmis.org
Subject: [PATCH -tip] perf: Document of netdev-times perf script
Date: Fri, 17 Sep 2010 17:23:45 +0900	[thread overview]
Message-ID: <4C932591.5090101@jp.fujitsu.com> (raw)

This patch adds a document of netdev-times which is used by perf.
This document shows how to use it.

Signed-off-by: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
---
 tools/perf/Documentation/netdev-times.txt |   70 +++++++++++++++++++++++++++++
 1 files changed, 70 insertions(+), 0 deletions(-)

diff --git a/tools/perf/Documentation/netdev-times.txt b/tools/perf/Documentation/netdev-times.txt
new file mode 100644
index 0000000..a905650
--- /dev/null
+++ b/tools/perf/Documentation/netdev-times.txt
@@ -0,0 +1,70 @@
+netdev-times(1)
+===============
+
+NAME
+----
+netdev-times - Tool to analysis packets processing
+
+SYNOPSIS
+--------
+'perf trace record netdev-times' [<script>]
+or
+'perf trace report netdev-times' [<options>]
+
+DESCRIPTION
+-----------
+This script shows packets processing and processed time.
+There are two steps to use it:
+
+ 'perf trace record netdev-times' [<script>] to record the events
+ which relates to packets processing.
+
+ 'perf trace report netdev-times' [<options>] to report a time-chart of
+ pakcets processing and processed time.
+
+OPTIONS
+-------
+tx::
+	Show only transmited packets processing.
+
+rx::
+	Show only received packets procssing.
+
+dev=<device>::
+	Show processing on the specified device.
+
+debug::
+	Work with debug mode. It shows buffer status.
+
+EXAMPLES
+--------
+If you want to use this, you need to record a perf.data like following.
+
+ # perf trace record netdev-times [<script>]
+
+If you set script, perf gathers events until it ends.
+If not, you must do Ctrl-C to stop recording.
+
+And if you want a report from the recorded data,
+
+ # perf trace report netdev-times [<options>]
+
+If you use some options, you can limit an output.
+For example, if you want to show a process of received packets associated
+with eth4,
+
+#perf trace report netdev-times rx dev=eth4
+106133.171439sec cpu=0
+  irq_entry(+0.000msec irq=24:eth4)
+         |
+  softirq_entry(+0.006msec)
+         |
+         |---netif_receive_skb(+0.010msec skb=f2d15900 len=100)
+         |            |
+         |      skb_copy_datagram_iovec(+0.039msec 10291::10291)
+         |
+  napi_poll_exit(+0.022msec eth4)
+
+SEE ALSO
+--------
+linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-trace[1]


                 reply	other threads:[~2010-09-17  8:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C932591.5090101@jp.fujitsu.com \
    --to=sanagi.koki@jp.fujitsu.com \
    --cc=acme@ghostprotocols.net \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=rostedt@goodmis.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