From: patchwork-bot+netdevbpf@kernel.org
To: Cosmin Ratiu <cratiu@nvidia.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net, razor@blackwall.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, jianbol@nvidia.com,
borisp@nvidia.com, tariqt@nvidia.com,
linux-kselftest@vger.kernel.org, liuhangbin@gmail.com,
liali@redhat.com
Subject: Re: [PATCH net v3] bonding: Correctly support GSO ESP offload
Date: Tue, 28 Jan 2025 12:30:29 +0000 [thread overview]
Message-ID: <173806742905.3778420.4837023666032645594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250127104147.759658-1-cratiu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 27 Jan 2025 12:41:47 +0200 you wrote:
> The referenced fix is incomplete. It correctly computes
> bond_dev->gso_partial_features across slaves, but unfortunately
> netdev_fix_features discards gso_partial_features from the feature set
> if NETIF_F_GSO_PARTIAL isn't set in bond_dev->features.
>
> This is visible with ethtool -k bond0 | grep esp:
> tx-esp-segmentation: off [requested on]
> esp-hw-offload: on
> esp-tx-csum-hw-offload: on
>
> [...]
Here is the summary with links:
- [net,v3] bonding: Correctly support GSO ESP offload
https://git.kernel.org/netdev/net/c/9e6c4e6b605c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-28 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 10:41 [PATCH net v3] bonding: Correctly support GSO ESP offload Cosmin Ratiu
2025-01-27 10:45 ` Cosmin Ratiu
2025-01-27 13:27 ` Hangbin Liu
2025-01-27 23:25 ` Jay Vosburgh
2025-01-28 12:30 ` patchwork-bot+netdevbpf [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=173806742905.3778420.4837023666032645594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jianbol@nvidia.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=tariqt@nvidia.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