From: fengchengwen <fengchengwen@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: <anatoly.burakov@intel.com>, <david.hunt@intel.com>,
<sivaprasad.tummala@amd.com>, <huisong@huawei.com>,
<liuyonglong@huawei.com>,
Dengdui Huang <huangdengdui@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 1/2] examples/l3fwd: support specify link speed
Date: Mon, 24 Nov 2025 16:11:09 +0800 [thread overview]
Message-ID: <9b202324-caea-4a87-bc19-ba0ad1cbf8b4@huawei.com> (raw)
In-Reply-To: <551821a7-6836-420c-b62f-5a6168de9abe@huawei.com>
Kindly ping for upstream.
On 8/27/2025 7:01 PM, fengchengwen wrote:
> Reviewed-by: Chengwen Feng <fengchengwen@huawei.com>
>
> On 8/27/2025 9:31 AM, Dengdui Huang wrote:
>> Currently, l3fwd starts in auto-negotiation mode, but it may fail to
>> link up when auto-negotiation is not supported. Therefore, it is
>> necessary to support starting with a specified speed for port.
>>
>> Additionally, this patch does not support changing the duplex mode.
>> So speeds like 10M, 100M are not configurable using this method.
>>
>> Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
next prev parent reply other threads:[~2025-11-24 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 1:31 [PATCH 1/2] examples/l3fwd: support specify link speed Dengdui Huang
2025-08-27 1:31 ` [PATCH 2/2] examples/l3fwd-power: " Dengdui Huang
2025-08-27 11:02 ` fengchengwen
2025-08-27 11:01 ` [PATCH 1/2] examples/l3fwd: " fengchengwen
2025-11-24 8:11 ` fengchengwen [this message]
2025-11-24 16:13 ` David Marchand
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=9b202324-caea-4a87-bc19-ba0ad1cbf8b4@huawei.com \
--to=fengchengwen@huawei.com \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=huangdengdui@huawei.com \
--cc=huisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=sivaprasad.tummala@amd.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).