From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "lihuisong (C)" <lihuisong@huawei.com>,
Gregory Etelson <getelson@nvidia.com>,
dev@dpdk.org
Cc: matan@nvidia.com, rasland@nvidia.com,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH] app/testpmd: fix MAC header in csum forward engine
Date: Sun, 6 Nov 2022 12:49:56 +0300 [thread overview]
Message-ID: <9c27a0af-a6f8-fd0e-0b01-ed0d703ac20d@oktetlabs.ru> (raw)
In-Reply-To: <f95c5907-ab8d-950c-b255-9bb7db98c5b7@huawei.com>
On 10/27/22 07:05, lihuisong (C) wrote:
>
> 在 2022/10/26 19:07, Gregory Etelson 写道:
>> MLX5 SR-IOV TX engine will not transmit Ethernet frame
>> if destination MAC address matched local port address. The frame ether
>> looped-back to RX or dropped, depending on the port configuration.
>>
>> Application running over MLX5 SR-IOV port cannot transmit packet
>> polled from RX queue as-is. The packet Ethernet destination address
>> must be changed.
>>
>> The patch adds new run-time configuration parameter to the `csum`
>> forwarding engine to control MAC addresses configuration:
>>
>> testpmd> csum mac-swap on|off <port_id>
>>
>> `mac-swap on` replace MAC addresses.
>> `mac-swap off` keep Ethernet header unchanged.
>>
>> Fixes: 9b4ea7ae77fa ("app/testpmd: revert MAC update in checksum
>> forwarding")
>> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Huisong Li <lihuisong@huawei.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-11-06 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 11:07 Gregory Etelson
2022-10-27 4:05 ` lihuisong (C)
2022-11-06 9:49 ` Andrew Rybchenko [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=9c27a0af-a6f8-fd0e-0b01-ed0d703ac20d@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=lihuisong@huawei.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=rasland@nvidia.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).