DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Merve Orakcı" <merveorakci58@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK-pktgen Flows
Date: Mon, 4 Jan 2021 14:21:10 +0000	[thread overview]
Message-ID: <6431B1FB-D92E-48C5-9CCE-B3A60C622FC6@intel.com> (raw)
In-Reply-To: <CALtT+qZ6cbJdKERL7wsZ-ZAc9+TsKXNZBKRLP3fzT06op36GMA@mail.gmail.com>



> On Jan 3, 2021, at 10:03 AM, Merve Orakcı <merveorakci58@gmail.com> wrote:
> 
> Hi everyone, I will get flows using the "range" command. So I am reviewing
> documents and sample codes about this topic. I would like to ask a few
> things that I cannot understand. What is the flow generation procedure of
> range command? Take port 0 as an example. 128 different ip addresses and
> 2000 different port numbers are used for source and destination. As far as
> I understand, these lines are repeated for each package.But how is the flow
> creation procedure?
> My opinions:
> First: Is it a random port number and ip address for each pass over the
> file? So total 128 * 2000= 256000 flows were created here.
> Second: when we think of increment operator, generated packets:
> 1. packet:  dst_ip: 192.168.1.1  ,  src_ip:  192.168.0.1 , dst_port: 2000 ,
> src_port: 5000
> 2. packet   dst_ip: 192.168.1.2  ,  src_ip:  192.168.0.2 , dst_port: 2001 ,
> src_port: 5001
> ................................
> 128. packet:   dst_ip: 192.168.1.128  ,  src_ip:  192.168.0.128 , dst_port:
> 2128 , src_port: 5128
> 129.packet      dst_ip: 192.168.1.1  ,  src_ip:  192.168.0.1 , dst_port:
> 2129, src_port: 5129  or (???)  dst_ip: 192.168.1.128  ,  src_ip:
> 192.168.0.128 , dst_port: 2129, src_port: 5129
> 
> then it will end when source and destination port numbers reach their
> highest value..
> 

The flow generation in Pktgen is pretty simple. Every time a packet is sent it fields you have setup are updated. This means if you have four fields setup to increment then they are changed for each packet sent. They are not random values as you can tell below.

> ........
> Can you help with this issue? I want to measure the performance of the
> system that I have created in different flow numbers with the pktgen tool.
> For this reason, the number of flows is important for me. Thanks for your
> help.
> 
> pktgen.range.dst_mac("0", "start", "3c:fd:fe:9c:5c:b8");
> 
> pktgen.range.src_mac("0", "start", "3c:fd:fe:9c:5c:d8");
> 
> pktgen.range.dst_ip("0", "start", "192.168.1.1");
> 
> pktgen.range.dst_ip("0", "inc", "0.0.0.1");
> 
> pktgen.range.dst_ip("0", "min", "192.168.1.1");
> 
> pktgen.range.dst_ip("0", "max", "192.168.1.128");
> 
> pktgen.range.src_ip("0", "start", "192.168.0.1");
> 
> pktgen.range.src_ip("0", "inc", "0.0.0.1");
> 
> pktgen.range.src_ip("0", "min", "192.168.0.1");
> 
> 
> pktgen.range.src_ip("0", "max", "192.168.0.128");
> 
> pktgen.set_proto("0", "udp");
> 
> pktgen.range.dst_port("0", "start", 2000);
> 
> pktgen.range.dst_port("0", "inc", 1);
> 
> pktgen.range.dst_port("0", "min", 2000);
> 
> pktgen.range.dst_port("0", "max", 4000);
> 
> pktgen.range.src_port("0", "start", 5000);
> 
> pktgen.range.src_port("0", "inc", 1);
> 
> pktgen.range.src_port("0", "min", 5000);
> 
> pktgen.range.src_port("0", "max", 7000);
> 
> pktgen.range.pkt_size("0", "start", 64);
> 
> pktgen.range.pkt_size("0", "inc", 0);
> 
> pktgen.range.pkt_size("0", "min", 64);
> 
> pktgen.range.pkt_size("0", "max", 256);
> 
> -- Set up second port
> 
> pktgen.range.dst_mac("1", "start", "3c:fd:fe:9c:5c:d8");
> 
> pktgen.range.src_mac("1", "start", "3c:fd:fe:9c:5c:b8");
> 
> 
> pktgen.range.dst_ip("1", "start", "192.168.0.1");
> 
> pktgen.range.dst_ip("1", "inc", "0.0.0.1");
> 
> pktgen.range.dst_ip("1", "min", "192.168.0.1");
> 
> pktgen.range.dst_ip("1", "max", "192.168.0.128");
> 
> pktgen.range.src_ip("1", "start", "192.168.1.1");
> 
> pktgen.range.src_ip("1", "inc", "0.0.0.1");
> 
> pktgen.range.src_ip("1", "min", "192.168.1.1");
> 
> pktgen.range.src_ip("1", "max", "192.168.1.128");
> 
> pktgen.set_proto("all", "udp");
> 
> pktgen.range.dst_port("1", "start", 5000);
> 
> pktgen.range.dst_port("1", "inc", 1);
> 
> pktgen.range.dst_port("1", "min", 5000);
> 
> pktgen.range.dst_port("1", "max", 7000);
> 
> pktgen.range.src_port("1", "start", 2000);
> 
> pktgen.range.src_port("1", "inc", 1);
> 
> pktgen.range.src_port("1", "min", 2000);
> 
> pktgen.range.src_port("1", "max", 4000);
> 
> pktgen.range.pkt_size("1", "start", 64);
> 
> pktgen.range.pkt_size("1", "inc", 0);
> 
> pktgen.range.pkt_size("1", "min", 64);
> 
> pktgen.range.pkt_size("1", "max", 256);
> 
> pktgen.set_range("all", "on");
> 
> -- 
> *Merve Orakcı*
> Research Asistant
> Gazi University - Institute of Informatics
> Computer Forensics
> Phone :+90 0312 202 3814


  reply	other threads:[~2021-01-04 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 16:03 Merve Orakcı
2021-01-04 14:21 ` Wiles, Keith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-21 20:11 Merve Orakcı
2020-12-22 16:04 ` Wiles, Keith

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=6431B1FB-D92E-48C5-9CCE-B3A60C622FC6@intel.com \
    --to=keith.wiles@intel.com \
    --cc=merveorakci58@gmail.com \
    --cc=users@dpdk.org \
    /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;
as well as URLs for NNTP newsgroup(s).