[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165183661369.26942.12493737757589783291.git-patchwork-notify@kernel.org>
Date: Fri, 06 May 2022 11:30:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, alexander.duyck@...il.com,
stephen@...workplumber.org
Subject: Re: [PATCH net-next 0/4] net: disambiguate the TSO and GSO limits
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:
On Thu, 5 May 2022 19:51:30 -0700 you wrote:
> This series separates the device-reported TSO limitations
> from the user space-controlled GSO limits. It used to be that
> we only had the former (HW limits) but they were named GSO.
> This probably lead to confusion and letting user override them.
>
> The problem came up in the BIG TCP discussion between Eric and
> Alex, and seems like something we should address.
>
> [...]
Here is the summary with links:
- [net-next,1/4] net: add netif_inherit_tso_max()
https://git.kernel.org/netdev/net-next/c/6df6398f7c8b
- [net-next,2/4] net: don't allow user space to lift the device limits
https://git.kernel.org/netdev/net-next/c/14d7b8122fd5
- [net-next,3/4] net: make drivers set the TSO limit not the GSO limit
https://git.kernel.org/netdev/net-next/c/ee8b7a1156f3
- [net-next,4/4] net: move netif_set_gso_max helpers
https://git.kernel.org/netdev/net-next/c/744d49daf8bd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists