From: patchwork-bot+netdevbpf@kernel.org
To: Ronak Doshi <ronak.doshi@broadcom.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
guolin.yang@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, ronghua@vmware.com,
sbhatewara@vmware.com, bhavesh@vmware.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] vmxnet3: update MTU after device quiesce
Date: Fri, 16 May 2025 23:10:35 +0000 [thread overview]
Message-ID: <174743703575.4089123.13792303088374756172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250515190457.8597-1-ronak.doshi@broadcom.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 15 May 2025 19:04:56 +0000 you wrote:
> Currently, when device mtu is updated, vmxnet3 updates netdev mtu, quiesces
> the device and then reactivates it for the ESXi to know about the new mtu.
> So, technically the OS stack can start using the new mtu before ESXi knows
> about the new mtu.
>
> This can lead to issues for TSO packets which use mss as per the new mtu
> configured. This patch fixes this issue by moving the mtu write after
> device quiesce.
>
> [...]
Here is the summary with links:
- [net,v2] vmxnet3: update MTU after device quiesce
https://git.kernel.org/netdev/net/c/43f0999af011
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-05-16 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 19:04 Ronak Doshi
2025-05-16 23:10 ` 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=174743703575.4089123.13792303088374756172.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhavesh@vmware.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guolin.yang@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ronak.doshi@broadcom.com \
--cc=ronghua@vmware.com \
--cc=sbhatewara@vmware.com \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®