From: "Wiles, Keith" <keith.wiles@intel.com>
To: Dheeraj Dang <dheerajdang138@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Generate more than 10000 flows.
Date: Mon, 8 May 2017 13:42:12 +0000 [thread overview]
Message-ID: <96F1ADF5-5A09-494D-ADA3-743FDDC3FB59@intel.com> (raw)
In-Reply-To: <CAJyVW4-G5Ewehtp8iQ4YBF77VEreOb+Ejjox0=Pqj7U1v2YpcA@mail.gmail.com>
> On May 7, 2017, at 11:05 AM, Dheeraj Dang <dheerajdang138@gmail.com> wrote:
>
> Hi,
>
> I m running dpdk pktgen between two virtual machines that are on the same
> network. Sender machine is sending UDP packets using range.
> I m trying to generate no of flows in dpdk-pktgen and for that purpose, I'm
> using source and destination port options (max, min, increment and start).
>
> Start Min Max Inc
> Source Port 3000 3000 3000+N 1
> Destination Port 4000 4000 4000+N 1
>
> where N is no of flows that I want to generate using dpdk-pktgen.
>
> Following are my observations with dpdk-pktgen.
>
> *N* *No of flows generated (sender side)*
> 10 10
> 100 100
> 1000 1000
> 10000 8192
> 20000 8192
In pktgen the range and other modes setup the 8192 packets allocated just before sending the frames. The reason you only get 8192 is that is the number of packet buffers allocated. In the app/pktgen-constants.h change the following line by increasing the ‘8’ to something larger. This value will increase the number of packets created per port so the amount used for memory will increase.
MAX_MBUFS_PER_PORT = (DEFAULT_TX_DESC * 8),/* number of buffers to support per port */
>
> Is it possible to generate more than 10000 flows through dpdk-pktgen ?
>
> Regards,
> Dheeraj Dang
Regards,
Keith
next prev parent reply other threads:[~2017-05-08 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 16:05 Dheeraj Dang
2017-05-08 13:42 ` Wiles, Keith [this message]
2017-05-09 4:41 ` Dheeraj Dang
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=96F1ADF5-5A09-494D-ADA3-743FDDC3FB59@intel.com \
--to=keith.wiles@intel.com \
--cc=dheerajdang138@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).