From: "Wiles, Keith" <keith.wiles@intel.com>
To: Bichan.Lu <Bichan.Lu@advantech.com.tw>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] pktgen-dpdk runts when start size is 64
Date: Thu, 8 Nov 2018 13:48:43 +0000 [thread overview]
Message-ID: <71F32FA1-4932-4EF2-9DE9-D81978612921@intel.com> (raw)
In-Reply-To: <5825f8fd096d486eb8bce95502704f30@ACLDAG.ADVANTECH.CORP>
> On Nov 8, 2018, at 2:12 AM, Bichan.Lu <Bichan.Lu@advantech.com.tw> wrote:
>
> Hi,
>
> OS: CentOS 7.5.1804
> Pktgen version: pktgen-3.5.8
> DPDK verison: dpdk-18.08
>
> I use the pktgen in follows command. When I start pktgen, default PktSize is 64, in the command I sad:
>
> ./pktgen -l 0-4 -n 3 -- -P -m "[1:3].0,[2:4].1"
> Pktgen:/> start all
>
> Link State : <UP-1000-FD> <UP-1000-FD> ----TotalRate----
> Pkts/s Max/Rx : 1487853/1487844 1491609/1491602 2979462/2979446
> Max/Tx : 1491607/1491606 1487855/1487841 2979459/2979447
> MBits/s Rx/Tx : 999/1002 1002/999 2002/2002
> Broadcast : 0 0
> Multicast : 0 0
> 64 Bytes : 0 0
> 65-127 : 0 0
> 128-255 : 0 0
> 256-511 : 0 0
> 512-1023 : 0 0
> 1024-1518 : 0 0
> Runts/Jumbos : 8889515/0 8913610/0
> Errors Rx/Tx : 0/0 0/0
> ......< shown parts of pktgen >.....
>
> Then will be get Runts.
> I tried when size is 68, range will be in [64 Bytes], and no runts.
> Pktgen:/> set 0 size 68
> Pktgen:/> set 1 size 68
> Pktgen:/> start all
>
What is the hardware NIC as most of the hardware appends the FCS?
Pktgen expects the NIC to append the FCS and there is a flag to disable that feature?
> I guess it may related about range, could help to check?
> Thanks.
>
> Best regards,
> Bichan.Lu
Regards,
Keith
next prev parent reply other threads:[~2018-11-08 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 2:12 Bichan.Lu
2018-11-08 13:48 ` Wiles, Keith [this message]
2018-11-12 10:02 ` Bichan.Lu
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=71F32FA1-4932-4EF2-9DE9-D81978612921@intel.com \
--to=keith.wiles@intel.com \
--cc=Bichan.Lu@advantech.com.tw \
--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).