From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Dongdong Liu <liudongdong3@huawei.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <yuying.zhang@intel.com>,
<stable@dpdk.org>, Huisong Li <lihuisong@huawei.com>,
Min Hu <humin29@huawei.com>, Xiaoyun Li <xiaoyun.li@intel.com>,
Aman Singh <aman.deep.singh@intel.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH v6] app/testpmd: add help messages for multi-process
Date: Thu, 9 Jun 2022 15:58:07 +0100 [thread overview]
Message-ID: <a56113b0-7722-cffc-03a9-e8248f5d5d1e@xilinx.com> (raw)
In-Reply-To: <00be91fd-81c2-4d48-f912-9872f872b494@xilinx.com>
On 6/9/2022 3:06 PM, Ferruh Yigit wrote:
> On 6/9/2022 9:52 AM, Dongdong Liu wrote:
>
>>
>> From: Huisong Li <lihuisong@huawei.com>
>>
>> This patch adds help messages for multi-process.
>> --num-procs=N: set the total number of multi-process instances.
>> --proc-id=id: set the id of the current process from multi-process
>> instances(0 <= id < num-procs).
>>
>> Fixes: a550baf24af9 ("app/testpmd: support multi-process")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>> Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
Acked-by: Ferruh Yigit <ferruh.yigit@xilinx.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-06-09 14:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 3:26 [PATCH] " Min Hu (Connor)
2022-02-28 8:57 ` Thomas Monjalon
2022-03-01 3:41 ` Min Hu (Connor)
2022-03-01 8:36 ` Thomas Monjalon
2022-03-01 9:19 ` Min Hu (Connor)
2022-03-01 3:39 ` [PATCH v2] " Min Hu (Connor)
2022-03-01 8:35 ` Thomas Monjalon
2022-03-01 9:17 ` Min Hu (Connor)
2022-03-01 9:16 ` [PATCH v3] " Min Hu (Connor)
2022-03-03 12:09 ` Ferruh Yigit
2022-03-03 14:59 ` Ajit Khaparde
2022-03-04 1:28 ` Min Hu (Connor)
2022-03-04 1:22 ` [PATCH] 1 version Min Hu (Connor)
2022-03-04 1:22 ` [PATCH] app/testpmd: add help messages for multi-process Min Hu (Connor)
2022-03-04 1:25 ` Min Hu (Connor)
2022-03-04 1:22 ` [PATCH] dpdk: show dev basic info Min Hu (Connor)
2022-03-04 1:25 ` Min Hu (Connor)
2022-03-04 1:22 ` [PATCH v4] ethdev: introduce dump API Min Hu (Connor)
2022-03-04 1:26 ` Min Hu (Connor)
2022-03-04 1:22 ` [PATCH] net/bonding: fix slaves initializing on mtu setting Min Hu (Connor)
2022-03-04 1:27 ` Min Hu (Connor)
2022-03-04 1:25 ` [PATCH] 1 version Min Hu (Connor)
2022-03-04 1:27 ` [PATCH v4] app/testpmd: add help messages for multi-process Min Hu (Connor)
2022-03-04 2:50 ` Zhang, Yuying
2022-03-04 6:29 ` Min Hu (Connor)
2022-03-04 6:26 ` [PATCH v5] " Min Hu (Connor)
2022-03-04 9:11 ` Zhang, Yuying
2022-03-04 15:35 ` Ferruh Yigit
2022-03-06 22:52 ` Thomas Monjalon
2022-03-07 1:05 ` Min Hu (Connor)
2022-03-04 14:46 ` Ferruh Yigit
2022-03-07 1:04 ` Min Hu (Connor)
2022-04-25 6:51 ` Min Hu (Connor)
2022-06-02 2:24 ` Min Hu (Connor)
2022-06-02 23:08 ` Ferruh Yigit
2022-06-09 8:07 ` Dongdong Liu
2022-06-09 8:52 ` [PATCH v6] " Dongdong Liu
2022-06-09 14:06 ` Ferruh Yigit
2022-06-09 14:58 ` Ferruh Yigit [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=a56113b0-7722-cffc-03a9-e8248f5d5d1e@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xiaoyun.li@intel.com \
--cc=yuying.zhang@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).