linux/samples/pktgen
Daniel T. Lee fa2f23e6a8 samples: pktgen: fix proc_cmd command result check logic
[ Upstream commit 3cad8f9115 ]

Currently, proc_cmd is used to dispatch command to 'pg_ctrl', 'pg_thread',
'pg_set'. proc_cmd is designed to check command result with grep the
"Result:", but this might fail since this string is only shown in
'pg_thread' and 'pg_set'.

This commit fixes this logic by grep-ing the "Result:" string only when
the command is not for 'pg_ctrl'.

For clarity of an execution flow, 'errexit' flag has been set.

To cleanup pktgen on exit, trap has been added for EXIT signal.

Signed-off-by: Daniel T. Lee <danieltimlee@gmail.com>
Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2019-12-31 16:43:45 +01:00
..
functions.sh samples: pktgen: fix proc_cmd command result check logic 2019-12-31 16:43:45 +01:00
parameters.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_bench_xmit_mode_netif_receive.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_bench_xmit_mode_queue_xmit.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_sample01_simple.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_sample02_multiqueue.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_sample03_burst_single_flow.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_sample04_many_flows.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_sample05_flow_per_thread.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
pktgen_sample06_numa_awared_queue_irq_affinity.sh samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00
README.rst samples: pktgen: allow to specify destination port 2019-07-01 11:02:20 -07:00

Sample and benchmark scripts for pktgen (packet generator)
==========================================================
This directory contains some pktgen sample and benchmark scripts, that
can easily be copied and adjusted for your own use-case.

General doc is located in kernel: Documentation/networking/pktgen.txt

Helper include files
====================
This directory contains two helper shell files, that can be "included"
by shell source'ing.  Namely "functions.sh" and "parameters.sh".

Common parameters
-----------------
The parameters.sh file support easy and consistant parameter parsing
across the sample scripts.  Usage example is printed on errors::

 Usage: ./pktgen_sample01_simple.sh [-vx] -i ethX
  -i : ($DEV)       output interface/device (required)
  -s : ($PKT_SIZE)  packet size
  -d : ($DEST_IP)   destination IP
  -m : ($DST_MAC)   destination MAC-addr
  -p : ($DST_PORT)  destination PORT range (e.g. 433-444) is also allowed
  -t : ($THREADS)   threads to start
  -f : ($F_THREAD)  index of first thread (zero indexed CPU number)
  -c : ($SKB_CLONE) SKB clones send before alloc new SKB
  -n : ($COUNT)     num messages to send per thread, 0 means indefinitely
  -b : ($BURST)     HW level bursting of SKBs
  -v : ($VERBOSE)   verbose
  -x : ($DEBUG)     debug

The global variable being set is also listed.  E.g. the required
interface/device parameter "-i" sets variable $DEV.

Common functions
----------------
The functions.sh file provides; Three different shell functions for
configuring the different components of pktgen: pg_ctrl(), pg_thread()
and pg_set().

These functions correspond to pktgens different components.
 * pg_ctrl()   control "pgctrl" (/proc/net/pktgen/pgctrl)
 * pg_thread() control the kernel threads and binding to devices
 * pg_set()    control setup of individual devices

See sample scripts for usage examples.