netsniff-ng: Fix typo Unkown -> Unknown - netsniff-ng.git - A high-performance Linux networking toolkit

diff options

author	Kartik Mistry <kartik.mistry@gmail.com>	2015-05-09 20:16:50 +0530
committer	Tobias Klauser <tklauser@distanz.ch>	2015-05-11 10:53:35 +0200
commit	75162e7efe04bfc2bad6b0268bb562628ba0baf6 (patch)
tree	9ca3e3f48a0640321ab3096bed329a271325fb5c /ioops.h
parent	9118e9e8673eb88ebf4f7af33d8ed9856f3ed554 (diff)

netsniff-ng: Fix typo Unkown -> Unknown

Fix typo in error message. Signed-off-by: Kartik Mistry <kartik.mistry@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>

Diffstat (limited to 'ioops.h')

0 files changed, 0 insertions, 0 deletions

rs typically do using the more complicated script-based tracing tools, at least during the initial stages of an investigation, can be accomplished by simply specifying a set of keys and values to be used in the creation of a hash table. The Linux kernel trace event subsystem happens to provide an extensive list of keys and values ready-made for such a purpose in the form of the event format files associated with each trace event. By simply consulting the format file for field names of interest and by plugging them into the hist trigger command, users can create an endless number of useful aggregations to help with investigating various properties of the system. See Documentation/trace/events.txt for examples. hist triggers are implemented on top of the existing event trigger infrastructure, and as such are consistent with the existing triggers from a user's perspective as well. The basic syntax follows the existing trigger syntax. Users start an aggregation by writing a 'hist' trigger to the event of interest's trigger file: # echo hist:keys=xxx [ if filter] > event/trigger Once a hist trigger has been set up, by default it continually aggregates every matching event into a hash table using the event key and a value field named 'hitcount'. To view the aggregation at any point in time, simply read the 'hist' file in the same directory as the 'trigger' file: # cat event/hist The detailed syntax provides additional options for user control, and is described exhaustively in Documentation/trace/events.txt and in the virtual tracing/README file in the tracing subsystem. Link: http://lkml.kernel.org/r/72d263b5e1853fe9c314953b65833c3aa75479f2.1457029949.git.tom.zanussi@linux.intel.com Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Tested-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> Reviewed-by: Namhyung Kim <namhyung@kernel.org> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

Diffstat (limited to 'kernel/trace')


context:
space:
mode: