pktgen scripts
Subsystems (2)
Hi Alexei,
I've cleaned up my pktgen scripts[1]. Do you think we should add them instead of the sample scripts in "samples/pktgen/pktgen.conf-*" ?
The main difference is I'm replacing the "pgset" with functions not needing global variable $PGDEV. Three new functions reflect pktgen's 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
I've named the sample scripts: "pktgen_sample{01,02,03}_desc.sh" in-order to suggest a reading order.
I've also added a script named: "pktgen_bench_xmit_mode_netif_receive.sh" which is basically your ingress benchmarking script.
[1] https://github.com/netoptimizer/network-testing/tree/master/pktgen
Signature · 5 lines
Best regards, Jesper Dangaard Brouer MSc.CS, Sr. Network Kernel Developer at Red Hat Author of http://www.iptv-analyzer.org LinkedIn: http://www.linkedin.com/in/brouer
Quoted 4 lines · Jesper Dangaard Brouer
Hi Alexei,
I've cleaned up my pktgen scripts[1]. Do you think we should add them instead of the sample scripts in "
samples/pktgen/pktgen.conf-*" ?
+1
Quoted 7 lines
The main difference is I'm replacing the "pgset" with functions not needing global variable $PGDEV. Three new functions reflect pktgen's 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
Quoted 6 lines
I've named the sample scripts: "pktgen_sample{01,02,03}_desc.sh" in-order to suggest a reading order.
I've also added a script named: "pktgen_bench_xmit_mode_netif_receive.sh" which is basically your ingress benchmarking script.[1] https://github.com/netoptimizer/network-testing/tree/master/pktgen
Looks great!! Much better than old samples/pktgen/. Could you add a readme file as well with few command line examples? It wasn't obvious how '-b' and other flags are working. I guess if somebody just tries to run them, the 'usage' function will explain things too.