From: Thomas Monjalon <thomas@monjalon.net>
To: "Zhang, Yuying" <yuying.zhang@intel.com>,
"Min Hu (Connor)" <humin29@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Huisong Li <lihuisong@huawei.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v5] app/testpmd: add help messages for multi-process
Date: Sun, 06 Mar 2022 23:52:28 +0100 [thread overview]
Message-ID: <5269403.vfdyTQepKt@thomas> (raw)
In-Reply-To: <1a9abf77-b0ed-d454-2c41-cca738712e08@intel.com>
04/03/2022 16:35, Ferruh Yigit:
> On 3/4/2022 9:11 AM, Zhang, Yuying wrote:
> > From: Min Hu (Connor) <humin29@huawei.com>
> >> From: Huisong Li <lihuisong@huawei.com>
> >>
> >> This patch adds help messages for multi-process.
> >> --num-procs <N>, where N is the total number of symmetric_mp instances
> >> that will be run side-by-side to perform packet processing. This parameter is
> >> used to configure the appropriate number of receive queues on each
> >> network port.
> >>
> >> --proc-id <n>, where n is a numeric value in the range 0 <= n < N (number of
> >> processes, specified above). This identifies which symmetric_mp instance is
> >> being run, so that each process can read a unique receive queue on each
> >> network port.
> >>
> >> 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>
> >
> > Acked-by: Yuying Zhang <yuying.zhang@intel.com>
> >
>
> Updated 'symmetric_mp' -> 'multi-process', with this change
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied to dpdk-next-net/main, thanks.
Why not reusing these defines?
#define PARAM_PROC_ID "proc-id"
#define PARAM_NUM_PROCS "num-procs"
Why not having "N" in the help messages like others?
I won't pull it in main.
Please rework and try to improve the description to make it shorter
and easier to understand.
next prev parent reply other threads:[~2022-03-06 22:52 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 [this message]
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
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=5269403.vfdyTQepKt@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=lihuisong@huawei.com \
--cc=stable@dpdk.org \
--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).