From: "lihuisong (C)" <lihuisong@huawei.com>
To: Chengwen Feng <fengchengwen@huawei.com>, <thomas@monjalon.net>,
<stephen@networkplumber.org>
Cc: <dev@dpdk.org>, <aman.deep.singh@intel.com>,
<liuyonglong@huawei.com>, <yangxingui@huawei.com>,
<lihuisong@huawei.com>
Subject: Re: [PATCH v7 1/2] app/testpmd: support specify TCs when DCB forward
Date: Wed, 12 Nov 2025 10:29:44 +0800 [thread overview]
Message-ID: <4e792aa5-7747-483d-bc30-d73ff4b5deb7@huawei.com> (raw)
In-Reply-To: <20251111091303.39491-2-fengchengwen@huawei.com>
在 2025/11/11 17:13, Chengwen Feng 写道:
> This commit supports specify TCs when DCB forwarding, the command:
>
> set dcb fwd_tc (tc_mask)
>
> The background of this command: only some TCs are expected to generate
> traffic when the DCB function is tested based on txonly forwarding, we
> could use this command to specify TCs to be used.
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
LGTM,
Acked-by: lihuisong@huawei.com
>
next prev parent reply other threads:[~2025-11-12 2:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 4:09 [PATCH 0/3] testpmd support stop specify lcore Chengwen Feng
2025-11-04 4:09 ` [PATCH 1/3] app/testpmd: fix invalid txp when setup DCB forward Chengwen Feng
2025-11-04 4:09 ` [PATCH 2/3] app/testpmd: fix wrong Rx queues " Chengwen Feng
2025-11-04 4:09 ` [PATCH 3/3] app/testpmd: support stop specify lcore Chengwen Feng
2025-11-05 0:21 ` [PATCH 0/3] testpmd " Stephen Hemminger
2025-11-05 0:43 ` fengchengwen
2025-11-05 9:47 ` [PATCH v2 0/3] testpmd support pause/resume specify lcore's fwd Chengwen Feng
2025-11-05 9:47 ` [PATCH v2 1/3] app/testpmd: fix invalid txp when setup DCB forward Chengwen Feng
2025-11-05 9:47 ` [PATCH v2 2/3] app/testpmd: fix wrong Rx queues " Chengwen Feng
2025-11-05 9:47 ` [PATCH v2 3/3] app/testpmd: support pause/resume specify lcore Chengwen Feng
2025-11-05 18:59 ` [PATCH v2 0/3] testpmd support pause/resume specify lcore's fwd Stephen Hemminger
2025-11-06 0:34 ` fengchengwen
2025-11-06 12:49 ` [PATCH v3] app/testpmd: support specify TCs when DCB forward Chengwen Feng
2025-11-06 19:24 ` Stephen Hemminger
2025-11-07 0:57 ` fengchengwen
2025-11-07 0:53 ` [PATCH v4] " Chengwen Feng
2025-11-10 7:36 ` [PATCH v5 0/2] two enhance for testpmd DCB test Chengwen Feng
2025-11-10 7:36 ` [PATCH v5 1/2] app/testpmd: support specify TCs when DCB forward Chengwen Feng
2025-11-10 7:36 ` [PATCH v5 2/2] app/testpmd: support multi-cores process one TC Chengwen Feng
2025-11-10 9:42 ` [PATCH v6 0/2] two enhance for testpmd DCB test Chengwen Feng
2025-11-10 9:43 ` [PATCH v6 1/2] app/testpmd: support specify TCs when DCB forward Chengwen Feng
2025-11-10 9:43 ` [PATCH v6 2/2] app/testpmd: support multi-cores process one TC Chengwen Feng
2025-11-11 9:13 ` [PATCH v7 0/2] two enhance for testpmd DCB test Chengwen Feng
2025-11-11 9:13 ` [PATCH v7 1/2] app/testpmd: support specify TCs when DCB forward Chengwen Feng
2025-11-12 2:29 ` lihuisong (C) [this message]
2025-11-11 9:13 ` [PATCH v7 2/2] app/testpmd: support multi-cores process one TC Chengwen Feng
2025-11-12 2:32 ` lihuisong (C)
2025-11-12 1:34 ` [PATCH v7 0/2] two enhance for testpmd DCB test fengchengwen
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=4e792aa5-7747-483d-bc30-d73ff4b5deb7@huawei.com \
--to=lihuisong@huawei.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=yangxingui@huawei.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).