From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
Hariprasad Govindharajan <hariprasad.govindharajan@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, stephen@networkplumber.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v9] app/testpmd: add portlist option
Date: Wed, 12 Feb 2020 13:59:48 +0000 [thread overview]
Message-ID: <a3087cc2-8c02-31a8-bdd7-824b75e63e54@intel.com> (raw)
In-Reply-To: <f8a7ac2a-2a84-3776-f25b-5bca2cb9cf8a@intel.com>
On 2/12/2020 1:03 PM, Burakov, Anatoly wrote:
> On 12-Feb-20 10:29 AM, Hariprasad Govindharajan wrote:
>> In current version, we are setting the ports
>> using portmask. With portmask, we can use only
>> upto 64 ports. This portlist option enables the user
>> to use more than 64 ports.
>> Now we can specify the ports in 2 different ways
>> - Using portmask (-p [0x]nnn): mask must be in hex format
>> - Using portlist in the following format
>> --portlist <p1>[-p2][,p3[-p4],...]
>>
>> --portmask 0x2 is same as --portlist 1
>> --portmask 0x3 is same as --portlist 0-1
>>
>> Signed-off-by: Hariprasad Govindharajan <hariprasad.govindharajan@intel.com>
>> ---
>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2020-02-12 13:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 10:30 [dpdk-dev] [PATCH 0/2] app/testpmd: add portlist option to the testpmd Hariprasad Govindharajan
2020-01-27 10:30 ` [dpdk-dev] [PATCH 1/2] " Hariprasad Govindharajan
2020-01-31 16:22 ` [dpdk-dev] [PATCH v2] " Hariprasad Govindharajan
2020-01-31 17:41 ` [dpdk-dev] [PATCH v3] " Hariprasad Govindharajan
2020-02-03 16:53 ` [dpdk-dev] [PATCH v4] " Hariprasad Govindharajan
2020-02-04 16:48 ` [dpdk-dev] [PATCH v5] " Hariprasad Govindharajan
2020-02-05 10:42 ` Ferruh Yigit
2020-02-06 15:03 ` [dpdk-dev] [PATCH v6] " Hariprasad Govindharajan
2020-02-10 17:19 ` [dpdk-dev] [PATCH v7] app/testpmd: add portlist option Hariprasad Govindharajan
2020-02-11 12:00 ` Burakov, Anatoly
2020-02-11 15:37 ` Govindharajan, Hariprasad
2020-02-11 15:52 ` [dpdk-dev] [PATCH v8] " Hariprasad Govindharajan
2020-02-11 16:51 ` Burakov, Anatoly
2020-02-12 10:25 ` Govindharajan, Hariprasad
2020-02-12 10:29 ` [dpdk-dev] [PATCH v9] " Hariprasad Govindharajan
2020-02-12 13:03 ` Burakov, Anatoly
2020-02-12 13:59 ` Ferruh Yigit [this message]
2020-02-12 17:27 ` Lipiec, Herakliusz
2020-02-13 11:31 ` Ferruh Yigit
2020-01-27 10:30 ` [dpdk-dev] [PATCH 2/2] eal: add eal_parse_optionlist to parse user input Hariprasad Govindharajan
2020-01-28 17:35 ` Ferruh Yigit
2020-01-29 17:44 ` David Marchand
2020-01-29 18:07 ` Ferruh Yigit
2020-01-29 19:19 ` Stephen Hemminger
2020-01-31 11:25 ` Govindharajan, Hariprasad
2020-01-31 14:42 ` Govindharajan, Hariprasad
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=a3087cc2-8c02-31a8-bdd7-824b75e63e54@intel.com \
--to=ferruh.yigit@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hariprasad.govindharajan@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=stephen@networkplumber.org \
--cc=wenzhuo.lu@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).