DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Damien Clabaut <damien.clabaut@corp.ovh.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Issue with pktgen-dpdk replaying >1500bytes pcap on MCX4
Date: Wed, 11 Oct 2017 11:59:08 -0700	[thread overview]
Message-ID: <20171011185907.GA23268@yongseok-MBP.local> (raw)
In-Reply-To: <D74C7355-B8EF-40F5-BC4C-E98E59215EF0@intel.com>

On Thu, Sep 28, 2017 at 08:44:26PM +0000, Wiles, Keith wrote:
> 
> > On Sep 26, 2017, at 8:09 AM, Damien Clabaut <damien.clabaut@corp.ovh.com> wrote:
> > 
> > Hello Keith and thank you for your answer,
> > 
> > The goal is indeed to generate as much traffic per machine as possible (we use pktgen-dpdk to benchmark datacenter routers before putting them on production).
> > 
> > For this we use all available CPU power to send packets.
> > 
> > Following your suggestion, I modified my command to:
> > 
> > ./app/app/x86_64-native-linuxapp-gcc/pktgen -l 0-7 -- -m 1.0 -s 0:pcap/8500Bpp.pcap
> 
> 
> I just noticed you were sending 8500 byte frames and you have to modify Pktgen
> to increase the size of the mbufs in the mempool. I only configure the mbufs
> to 1518 byte buffers or really 2048 byte, but I only deal with 1518 max size.
> The size can be changed, but I am not next to a machine right now.

Hi Damien,

Could you manage to resolve this issue? Keith mentioned pktgen doesn't support
jumbo frames w/o modifying code. Do you still have an issue with Mellanox NIC
and its PMDs? Please let me know.

Thanks
Yongseok

  reply	other threads:[~2017-10-11 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 17:19 Damien Clabaut
2017-09-26  0:46 ` Yongseok Koh
2017-09-26 12:43   ` Damien Clabaut
2017-09-26  1:46 ` Wiles, Keith
2017-09-26 13:09   ` Damien Clabaut
2017-09-28 20:44     ` Wiles, Keith
2017-10-11 18:59       ` Yongseok Koh [this message]
2017-10-12 12:34         ` Damien Clabaut

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=20171011185907.GA23268@yongseok-MBP.local \
    --to=yskoh@mellanox.com \
    --cc=damien.clabaut@corp.ovh.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    /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).