From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: Huisong Li <lihuisong@huawei.com>, <stable@dpdk.org>,
Xiaoyun Li <xiaoyun.li@intel.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Lijun Ou <oulijun@huawei.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [PATCH] app/testpmd: add help messages for multi-process
Date: Fri, 4 Mar 2022 09:22:53 +0800 [thread overview]
Message-ID: <20220304012257.39247-2-humin29@huawei.com> (raw)
In-Reply-To: <20220304012257.39247-1-humin29@huawei.com>
From: Huisong Li <lihuisong@huawei.com>
This patch adds help messages for multi-process.
Fixes: a550baf24af9 ("app/testpmd: support multi-process")
Cc: stable@dpdk.org
Signed-off-by: Huisong Li <lihuisong@huawei.com>
---
app/test-pmd/parameters.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/app/test-pmd/parameters.c b/app/test-pmd/parameters.c
index 5251722d0f..6cc7afe15a 100644
--- a/app/test-pmd/parameters.c
+++ b/app/test-pmd/parameters.c
@@ -211,6 +211,8 @@ usage(char* progname)
printf(" --hairpin-mode=0xXX: bitmask set the hairpin port mode.\n"
" 0x10 - explicit Tx rule, 0x02 - hairpin ports paired\n"
" 0x01 - hairpin ports loop, 0x00 - hairpin port self\n");
+ printf(" --num-procs: the number of processes which will be used\n");
+ printf(" --proc-id : the id of the current process (id < num-procs)\n");
}
#ifdef RTE_LIB_CMDLINE
--
2.33.0
next prev parent reply other threads:[~2022-03-04 1:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 3:26 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 ` Min Hu (Connor) [this message]
2022-03-04 1:25 ` [PATCH] app/testpmd: add help messages for multi-process 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
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=20220304012257.39247-2-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=lihuisong@huawei.com \
--cc=oulijun@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).