DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Sara Gittlin <sara.gittlin@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] pktgen range stop/start all
Date: Tue, 11 Jun 2019 19:26:40 +0000	[thread overview]
Message-ID: <19173AB6-FAD3-4A4F-8BE7-41515487156A@intel.com> (raw)
In-Reply-To: <CAA_4wjYnDwYB0kuBj+7uqjh_E7ED56iuC-CPFce10PsJp4nHKg@mail.gmail.com>



> On Jun 11, 2019, at 1:59 PM, Sara Gittlin <sara.gittlin@gmail.com> wrote:
> 
> Keith
> the 5 tuples are always within the range. but when i stop/start i see added/different 5 tuples sessions that were not seen before.   but all are within the range

The reason is I did not reset the internal values I used to create the original list of mbufs to the original values and this is why you get a new set of values. :-)
> Thank you
> -Sara
> 
> On Tue, Jun 11, 2019 at 9:28 PM Wiles, Keith <keith.wiles@intel.com> wrote:
> The 5 tuples should stay within the range you had defined, if not then that is a bug.
> 
> > On Jun 11, 2019, at 1:08 PM, Sara Gittlin <sara.gittlin@gmail.com> wrote:
> > 
> > Hi
> > i've enabled the pktgen range feature.  and i see that whenever i stop all
> > and start all a different / additional sessions  are transmitted .
> > my range are src/dst IP  and src/dst/Ports. whenever i stop all and start
> > all  a   different/additional sessions 5 tuples sessions are transmitted .
> > (dst/src IP , dst/src P:orts and IP type)
> > is this a normal behaviour ?   for my purposes  it is very good behaviour
> > 
> > Regards
> > -Sara
> 
> Regards,
> Keith
> 

Regards,
Keith


  reply	other threads:[~2019-06-11 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 18:08 Sara Gittlin
2019-06-11 18:28 ` Wiles, Keith
2019-06-11 18:59   ` Sara Gittlin
2019-06-11 19:26     ` Wiles, Keith [this message]
2019-06-11 19:34       ` Sara Gittlin

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=19173AB6-FAD3-4A4F-8BE7-41515487156A@intel.com \
    --to=keith.wiles@intel.com \
    --cc=sara.gittlin@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).