From: patchwork-bot+netdevbpf@kernel.org
To: Shradha Gupta <shradhagupta@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, longli@microsoft.com,
kotaranov@microsoft.com, schakrabarti@linux.microsoft.com,
erick.archer@outlook.com, shradhagupta@microsoft.com
Subject: Re: [PATCH v3 net-next 0/2] Enable Big TCP for MANA devices
Date: Wed, 19 Feb 2025 09:50:31 +0000 [thread overview]
Message-ID: <173995863100.531989.91959446814814394.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1739763715-28412-1-git-send-email-shradhagupta@linux.microsoft.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Sun, 16 Feb 2025 19:41:55 -0800 you wrote:
> Allow the max gso/gro aggregated pkt size to go up to GSO_MAX_SIZE for
> MANA NIC. On Azure, this not possible without allowing the same for
> netvsc NIC (as the NICs are bonded together).
> Therefore, we use netif_set_tso_max_size() to set max aggregated pkt
> size
> to VF's tso_max_size for netvsc too, when the data path is switched over
> to the VF
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE
https://git.kernel.org/netdev/net-next/c/27315836f4bc
- [v3,net-next,2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF
https://git.kernel.org/netdev/net-next/c/685920920e3d
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-02-19 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 3:41 [PATCH v3 net-next 0/2] Enable Big TCP for MANA devices Shradha Gupta
2025-02-17 3:42 ` [PATCH v3 net-next 1/2] net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE Shradha Gupta
2025-02-17 3:42 ` [PATCH v3 net-next 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF Shradha Gupta
2025-02-19 9:50 ` 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=173995863100.531989.91959446814814394.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=erick.archer@outlook.com \
--cc=haiyangz@microsoft.com \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=schakrabarti@linux.microsoft.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=shradhagupta@microsoft.com \
--cc=wei.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.