07 Oct, 2019

2 commits

  • Currently, kernel pktgen has the feature to specify destination
    address range for sending packet. (e.g. pgset "dst_min/dst_max")

    But on samples, each pktgen script doesn't have any option to achieve this.

    This commit adds the feature to specify the destination address range with CIDR.

    -d : ($DEST_IP) destination IP. CIDR (e.g. 198.18.0.0/15) is also allowed

    # ./pktgen_sample01_simple.sh -6 -d fe80::20/126 -p 3000 -n 4
    # tcpdump ip6 and udp
    05:14:18.082285 IP6 fe80::99.71 > fe80::23.3000: UDP, length 16
    05:14:18.082564 IP6 fe80::99.43 > fe80::23.3000: UDP, length 16
    05:14:18.083366 IP6 fe80::99.107 > fe80::22.3000: UDP, length 16
    05:14:18.083585 IP6 fe80::99.97 > fe80::21.3000: UDP, length 16

    Signed-off-by: Daniel T. Lee
    Acked-by: Jesper Dangaard Brouer
    Signed-off-by: David S. Miller

    Daniel T. Lee
     
  • This commit changes variable names that can cause confusion.

    For example, variable DST_MIN is quite confusing since the
    keyword 'udp_dst_min' and keyword 'dst_min' is used with pg_ctrl.

    On the following commit, 'dst_min' will be used to set destination IP,
    and the existing variable name DST_MIN should be changed.

    Variable names are matched to the exact keyword used with pg_ctrl.

    Signed-off-by: Daniel T. Lee
    Acked-by: Jesper Dangaard Brouer
    Signed-off-by: David S. Miller

    Daniel T. Lee
     

02 Jul, 2019

1 commit

  • Currently, kernel pktgen has the feature to specify udp destination port
    for sending packet. (e.g. pgset "udp_dst_min 9")

    But on samples, each of the scripts doesn't have any option to achieve this.

    This commit adds the DST_PORT option to specify the target port(s) in the script.

    -p : ($DST_PORT) destination PORT range (e.g. 433-444) is also allowed

    Signed-off-by: Daniel T. Lee
    Acked-by: Jesper Dangaard Brouer
    Signed-off-by: David S. Miller

    Daniel T. Lee
     

02 Nov, 2017

1 commit

  • Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

17 Jun, 2017

2 commits


21 Jul, 2016

1 commit

  • Add a '-6' option to the sample pktgen scripts for sending out
    IPv6 packets.

    [root@kerneldev010.prn1 ~/pktgen]# ./pktgen_sample03_burst_single_flow.sh -i eth0 -s 64 -d fe80::f652:14ff:fec2:a14c -m f4:52:14:c2:a1:4c -b 32 -6

    [root@kerneldev011.prn1 ~]# tcpdump -i eth0 -nn -c3 port 9
    tcpdump: WARNING: eth0: no IPv4 address assigned
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
    14:38:51.815297 IP6 fe80::f652:14ff:fec2:2ad2.9 > fe80::f652:14ff:fec2:a14c.9: UDP, length 16
    14:38:51.815311 IP6 fe80::f652:14ff:fec2:2ad2.9 > fe80::f652:14ff:fec2:a14c.9: UDP, length 16
    14:38:51.815313 IP6 fe80::f652:14ff:fec2:2ad2.9 > fe80::f652:14ff:fec2:a14c.9: UDP, length 16

    Signed-off-by: Martin KaFai Lau
    Acked-by: Alexei Starovoitov
    Signed-off-by: David S. Miller

    Martin KaFai Lau
     

23 May, 2015

1 commit

  • This script pktgen_bench_xmit_mode_netif_receive.sh is a benchmark
    script, which can be used for benchmarking part of the network stack.
    This can be used for performance improving or catching regression in
    that area.

    The script is developed for benchmarking ingress qdisc path, original
    idea by Alexei Starovoitov. This script don't really need any
    hardware. This is achieved via the recently introduced stack inject
    feature "xmit_mode netif_receive". See commit 62f64aed622b6 ("pktgen:
    introduce xmit_mode ''").

    Signed-off-by: Jesper Dangaard Brouer
    Signed-off-by: David S. Miller

    Jesper Dangaard Brouer