From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>, rostedt@goodmis.org
Cc: daniel.wagner@bmw-carit.de, namhyung@kernel.org,
josh@joshtriplett.org, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 08/22] tracing: Add 'hist' event trigger command
Date: Mon, 20 Jul 2015 22:37:14 +0900 [thread overview]
Message-ID: <55ACF98A.9070307@hitachi.com> (raw)
In-Reply-To: <4912007a2c10ba09a34e5edafa7325377a4795d5.1437066836.git.tom.zanussi@linux.intel.com>
Hi Tom,
On 2015/07/17 2:22, Tom Zanussi wrote:
> @@ -3782,6 +3785,32 @@ static const char readme_msg[] =
> "\t To remove a trigger with a count:\n"
> "\t echo '!<trigger>:0 > <system>/<event>/trigger\n"
> "\t Filters can be ignored when removing a trigger.\n"
> +#ifdef CONFIG_HIST_TRIGGERS
> + " hist trigger\t- If set, event hits are aggregated into a hash table\n"
> + "\t Format: hist:keys=<field1>\n"
> + "\t [:size=#entries]\n"
> + "\t [if <filter>]\n\n"
> + "\t When a matching event is hit, an entry is added to a hash\n"
> + "\t table using the key named. Keys correspond to fields in the\n"
> + "\t event's format description. On an event hit, the value of a\n"
> + "\t sum called 'hitcount' is incremented, which is simply a count\n"
> + "\t of event hits. Keys can be any field.\n\n"
> + "\t Reading the 'hist' file for the event will dump the hash\n"
> + "\t table in its entirety to stdout. Each printed hash table\n"
> + "\t entry is a simple list of the keys and values comprising the\n"
> + "\t entry; keys are printed first and are delineated by curly\n"
> + "\t braces, and are followed by the set of value fields for the\n"
> + "\t entry. Numeric fields are displayed as base-10 integers.\n"
> + "\t By default, the size of the hash table is 2048 entries. The\n"
> + "\t 'size' param can be used to specify more or fewer than that.\n"
> + "\t The units are in terms of hashtable entries - if a run uses\n"
> + "\t more entries than specified, the results will show the number\n"
> + "\t of 'drops', the number of hits that were ignored. The size\n"
> + "\t should be a power of 2 between 128 and 131072 (any non-\n"
> + "\t power-of-2 number specified will be rounded up).\n\n"
> + "\t The entries are sorted by 'hitcount' and the sort order is\n"
> + "\t 'ascending'.\n\n"
Hmm, this seems too much about implementation of histogram. Could you shorten this
to be a half ?
Thank you,
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-07-20 13:37 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 17:22 [PATCH v9 00/22] tracing: 'hist' triggers Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 01/22] tracing: Update cond flag when enabling or disabling a trigger Tom Zanussi
2015-07-21 10:04 ` Masami Hiramatsu
2015-07-16 17:22 ` [PATCH v9 02/22] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2015-07-21 10:04 ` Masami Hiramatsu
2015-07-21 14:26 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 03/22] tracing: Make event trigger " Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 04/22] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 05/22] tracing: Add get_syscall_name() Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 06/22] tracing: Add a per-event-trigger 'paused' field Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 07/22] tracing: Add lock-free tracing_map Tom Zanussi
2015-07-16 17:49 ` Peter Zijlstra
2015-07-16 21:41 ` Tom Zanussi
2015-07-16 22:32 ` Peter Zijlstra
2015-07-17 1:51 ` Tom Zanussi
2015-07-16 18:03 ` Peter Zijlstra
2015-07-16 21:33 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 08/22] tracing: Add 'hist' event trigger command Tom Zanussi
2015-07-20 13:37 ` Masami Hiramatsu [this message]
2015-07-21 14:17 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 09/22] tracing: Add hist trigger support for multiple values ('vals=' param) Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 10/22] tracing: Add hist trigger support for compound keys Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 11/22] tracing: Add hist trigger support for user-defined sorting ('sort=' param) Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 12/22] tracing: Add hist trigger support for pausing and continuing a trace Tom Zanussi
2015-07-22 8:20 ` Masami Hiramatsu
2015-07-22 20:22 ` Tom Zanussi
2015-07-23 14:06 ` Masami Hiramatsu
2015-07-23 15:58 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 13/22] tracing: Add hist trigger support for clearing " Tom Zanussi
2015-07-22 13:50 ` Masami Hiramatsu
2015-07-22 20:24 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 14/22] tracing: Add hist trigger 'hex' modifier for displaying numeric fields Tom Zanussi
2015-07-19 13:22 ` Namhyung Kim
2015-07-21 14:10 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 15/22] tracing: Add hist trigger 'sym' and 'sym-offset' modifiers Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 16/22] tracing: Add hist trigger 'execname' modifier Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 17/22] tracing: Add hist trigger 'syscall' modifier Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 18/22] tracing: Add hist trigger support for stacktraces as keys Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 19/22] tracing: Support string type key properly Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 20/22] tracing: Remove restriction on string position in hist trigger keys Tom Zanussi
2015-07-19 13:31 ` Namhyung Kim
2015-07-21 14:15 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 21/22] tracing: Add enable_hist/disable_hist triggers Tom Zanussi
2015-07-20 14:57 ` Masami Hiramatsu
2015-07-21 16:10 ` Tom Zanussi
2015-07-22 14:21 ` Masami Hiramatsu
2015-07-22 20:18 ` Tom Zanussi
2015-07-16 17:22 ` [PATCH v9 22/22] tracing: Add 'hist' trigger Documentation Tom Zanussi
2015-07-21 9:40 ` [PATCH v9 00/22] tracing: 'hist' triggers Masami Hiramatsu
2015-07-21 14:18 ` Tom Zanussi
2015-07-22 18:29 ` Brendan Gregg
2015-07-23 1:55 ` Tom Zanussi
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=55ACF98A.9070307@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=andi@firstfloor.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.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