DPDK usage discussions
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] pktgen-dpdk range for udp proto seems not working
Date: Fri, 22 Apr 2016 11:42:35 -0700	[thread overview]
Message-ID: <CAK3+h2y7kJw=TWCp6WdFsvbkzRbAzFBm7aUtKOK2J=oRTP_uow@mail.gmail.com> (raw)
In-Reply-To: <CAK3+h2yLwor9vUU_6qOVsC2gvx_eW945OhA9wNr_XUJVrmxsbg@mail.gmail.com>

here is a diff to add the range.proto in help menu:

# git diff
diff --git a/app/cmd-functions.c b/app/cmd-functions.c
index b2fda7c..c348e73 100644
--- a/app/cmd-functions.c
+++ b/app/cmd-functions.c
@@ -303,6 +303,8 @@ const char *help_info[] = {
        "pkt.size max <portlist> value      - Set pkt size maximum address",
        "pkt.size inc <portlist> value      - Set pkt size increment address",
        "range <portlist> <state>           - Enable or Disable the
given portlist for sending a range of packets",
+       "range.proto <portlist> [tcp|udp|icmp]",
+       "                                   - Set ip proto for sending
a range of packets",
        "",
        "<<PageBreak>>",
        "       Flags: P---------------- - Promiscuous mode enabled",

I also noticed that the range.proto setting can not be saved when
running "save <path to file>" command, not sure how to patch that up.



On Fri, Apr 22, 2016 at 11:31 AM, Vincent Li <vincent.mc.li@gmail.com> wrote:
>>
>> Am I miss anything?
>
> sorry I missed the 'range.proto 0 udp' setting in the script file, the
> range setting is not in help menu, probably should update the help
> menu

  reply	other threads:[~2016-04-22 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 17:47 Vincent Li
2016-04-22 18:31 ` Vincent Li
2016-04-22 18:42   ` Vincent Li [this message]
2016-04-22 18:45     ` Wiles, Keith
2016-04-22 18:44   ` Wiles, Keith

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='CAK3+h2y7kJw=TWCp6WdFsvbkzRbAzFBm7aUtKOK2J=oRTP_uow@mail.gmail.com' \
    --to=vincent.mc.li@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).