DPDK patches and discussions
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <thomas@monjalon.net>, <dev@dpdk.org>,
	<aman.deep.singh@intel.com>, <liuyonglong@huawei.com>,
	<yangxingui@huawei.com>, <lihuisong@huawei.com>
Subject: Re: [PATCH v2 0/3] testpmd support pause/resume specify lcore's fwd
Date: Thu, 6 Nov 2025 08:34:30 +0800	[thread overview]
Message-ID: <14afcee7-c302-4f6a-a614-c7cad1e84363@huawei.com> (raw)
In-Reply-To: <20251105105946.73a06834@phoenix>

On 11/6/2025 2:59 AM, Stephen Hemminger wrote:
> On Wed, 5 Nov 2025 17:47:45 +0800
> Chengwen Feng <fengchengwen@huawei.com> wrote:
> 
>> This patch support pause/resume specify lcore's forwarding for testpmd,
>> and also include two bugfix which found when test DCB function.
>>
>> Chengwen Feng (3):
>>   app/testpmd: fix invalid txp when setup DCB forward
>>   app/testpmd: fix wrong Rx queues when setup DCB forward
>>   app/testpmd: support pause/resume specify lcore
>>
>>  app/test-pmd/cmdline.c                      | 126 ++++++++++++++++++++
>>  app/test-pmd/config.c                       |   9 +-
>>  app/test-pmd/testpmd.c                      |   5 +
>>  app/test-pmd/testpmd.h                      |   2 +-
>>  doc/guides/testpmd_app_ug/testpmd_funcs.rst |  14 +++
>>  5 files changed, 149 insertions(+), 7 deletions(-)
>>
> 
> Please split bug fix from enhancements.

done

> 
> The whole scheme looks like an optimization for power usage in testpmd.
> Since testpmd is solely focused on performance, I don't think you have
> provided enough justification to add the new feature.

I know your worry, especial in this cycles.

> 
> With DCB if there are TC's that could receive packets, it is better
> not to never poll those queues. 
> 
> That said, longer term it would make sense to bring of the power
> saving logic that is in examples into testpmd.

I will try to another way to meet the usage of specify TC.

Thanks


      reply	other threads:[~2025-11-06  0:34 UTC|newest]

Thread overview: 12+ 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 [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=14afcee7-c302-4f6a-a614-c7cad1e84363@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=lihuisong@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).