From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, alexander.duyck@gmail.com,
stephen@networkplumber.org
Subject: Re: [PATCH net-next 0/4] net: disambiguate the TSO and GSO limits
Date: Fri, 06 May 2022 11:30:13 +0000 [thread overview]
Message-ID: <165183661369.26942.12493737757589783291.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220506025134.794537-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2022-05-06 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 2:51 [PATCH net-next 0/4] net: disambiguate the TSO and GSO limits Jakub Kicinski
2022-05-06 2:51 ` [PATCH net-next 1/4] net: add netif_inherit_tso_max() Jakub Kicinski
2022-05-06 11:27 ` Simon Horman
2022-05-06 2:51 ` [PATCH net-next 2/4] net: don't allow user space to lift the device limits Jakub Kicinski
2022-05-06 2:51 ` [PATCH net-next 3/4] net: make drivers set the TSO limit not the GSO limit Jakub Kicinski
2022-05-06 11:30 ` Simon Horman
2022-05-09 14:31 ` Marcin Wojtas
2022-05-06 2:51 ` [PATCH net-next 4/4] net: move netif_set_gso_max helpers Jakub Kicinski
2022-05-06 2:58 ` [PATCH net-next 0/4] net: disambiguate the TSO and GSO limits Eric Dumazet
2022-05-06 11: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=165183661369.26942.12493737757589783291.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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.