DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Avi Cohen (A)" <avi.cohen@huawei.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] pktgen 3.2.4 - problem with set size
Date: Sun, 23 Apr 2017 13:15:32 +0000	[thread overview]
Message-ID: <C6468572-7B2A-4602-AF36-A3179C5CB311@intel.com> (raw)
In-Reply-To: <B84047ECBD981D4B93EAE5A6245AA361A1C590@lhreml501-mbb>

Thanks for the update.

> On Apr 23, 2017, at 1:42 AM, Avi Cohen (A) <avi.cohen@huawei.com> wrote:
> 
> Thank Keith
> As you said, stopping transmission is needed  before you change the pkt-size.
> So  everything is OK now for me. (the throughput is also OK -  ~10Gbps ) 
> Best Regards
> Avi
> 
>> -----Original Message-----
>> From: Wiles, Keith [mailto:keith.wiles@intel.com]
>> Sent: Wednesday, 19 April, 2017 5:17 PM
>> To: Avi Cohen (A)
>> Cc: users@dpdk.org
>> Subject: Re: [dpdk-users] pktgen 3.2.4 - problem with set size
>> 
>> I did find some issues with 3.2.4 and please try 3.2.6, but I do not think it will fix
>> the problem. When the size of the packet increases the packets per second
>> must decrease, right?
>> 
>> Now changing the size make sure you stop transmitting traffic first. The size
>> should change to whatever you set, but I am out of town and will have to wait
>> till I return to verify the problem.
>> 
>>> On Apr 19, 2017, at 3:59 AM, Avi Cohen (A) <avi.cohen@huawei.com> wrote:
>>> 
>>> Hello,
>>> When I set packet size - I see that the menu in the transmitter is updated,  but
>> in the receiver I always receive  64B pkt size.
>>> Also the throughput is degraded when I enlarge the pkt-size in the TX
>>> (which does not make sense) Best Regards avi
>> 
>> Regards,
>> Keith
> 

Regards,
Keith

      reply	other threads:[~2017-04-23 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 10:59 Avi Cohen (A)
2017-04-19 14:16 ` Wiles, Keith
2017-04-23  6:42   ` Avi Cohen (A)
2017-04-23 13:15     ` Wiles, Keith [this message]

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=C6468572-7B2A-4602-AF36-A3179C5CB311@intel.com \
    --to=keith.wiles@intel.com \
    --cc=avi.cohen@huawei.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).