public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Xin Long <lucien.xin@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
	edumazet@google•com, pabeni@redhat•com, dsahern@gmail•com,
	yoshfuji@linux-ipv6•org, pshelar@ovn•org, jhs@mojatatu•com,
	xiyou.wangcong@gmail•com, jiri@resnulli•us, pablo@netfilter•org,
	fw@strlen•de, marcelo.leitner@gmail•com, i.maximets@ovn•org,
	aconole@redhat•com, roopa@nvidia•com, razor@blackwall•org,
	maheshb@google•com, paul@paul-moore•com, gnault@redhat•com
Subject: Re: [PATCHv4 net-next 00/10] net: support ipv4 big tcp
Date: Thu, 02 Feb 2023 05:10:18 +0000	[thread overview]
Message-ID: <167531461888.3090.18277263241067373566.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1674921359.git.lucien.xin@gmail.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:

On Sat, 28 Jan 2023 10:58:29 -0500 you wrote:
> This is similar to the BIG TCP patchset added by Eric for IPv6:
> 
>   https://lwn.net/Articles/895398/
> 
> Different from IPv6, IPv4 tot_len is 16-bit long only, and IPv4 header
> doesn't have exthdrs(options) for the BIG TCP packets' length. To make
> it simple, as David and Paolo suggested, we set IPv4 tot_len to 0 to
> indicate this might be a BIG TCP packet and use skb->len as the real
> IPv4 total length.
> 
> [...]

Here is the summary with links:
  - [PATCHv4,net-next,01/10] net: add a couple of helpers for iph tot_len
    https://git.kernel.org/netdev/net-next/c/058a8f7f73aa
  - [PATCHv4,net-next,02/10] bridge: use skb_ip_totlen in br netfilter
    https://git.kernel.org/netdev/net-next/c/46abd17302ba
  - [PATCHv4,net-next,03/10] openvswitch: use skb_ip_totlen in conntrack
    https://git.kernel.org/netdev/net-next/c/ec84c955a0d0
  - [PATCHv4,net-next,04/10] net: sched: use skb_ip_totlen and iph_totlen
    https://git.kernel.org/netdev/net-next/c/043e397e48c5
  - [PATCHv4,net-next,05/10] netfilter: use skb_ip_totlen and iph_totlen
    https://git.kernel.org/netdev/net-next/c/a13fbf5ed5b4
  - [PATCHv4,net-next,06/10] cipso_ipv4: use iph_set_totlen in skbuff_setattr
    https://git.kernel.org/netdev/net-next/c/7eb072be41ba
  - [PATCHv4,net-next,07/10] ipvlan: use skb_ip_totlen in ipvlan_get_L3_hdr
    https://git.kernel.org/netdev/net-next/c/50e6fb5c6efb
  - [PATCHv4,net-next,08/10] packet: add TP_STATUS_GSO_TCP for tp_status
    https://git.kernel.org/netdev/net-next/c/8e08bb75b60f
  - [PATCHv4,net-next,09/10] net: add gso_ipv4_max_size and gro_ipv4_max_size per device
    https://git.kernel.org/netdev/net-next/c/9eefedd58ae1
  - [PATCHv4,net-next,10/10] net: add support for ipv4 big tcp
    https://git.kernel.org/netdev/net-next/c/b1a78b9b9886

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-02-02  5:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 15:58 [PATCHv4 net-next 00/10] net: support ipv4 big tcp Xin Long
2023-01-28 15:58 ` [PATCHv4 net-next 01/10] net: add a couple of helpers for iph tot_len Xin Long
2023-02-01 15:31   ` David Ahern
2023-01-28 15:58 ` [PATCHv4 net-next 02/10] bridge: use skb_ip_totlen in br netfilter Xin Long
2023-01-31 15:01   ` Nikolay Aleksandrov
2023-01-28 15:58 ` [PATCHv4 net-next 03/10] openvswitch: use skb_ip_totlen in conntrack Xin Long
2023-02-01 13:29   ` Aaron Conole
2023-01-28 15:58 ` [PATCHv4 net-next 04/10] net: sched: use skb_ip_totlen and iph_totlen Xin Long
2023-01-28 15:58 ` [PATCHv4 net-next 05/10] netfilter: " Xin Long
2023-01-28 15:58 ` [PATCHv4 net-next 06/10] cipso_ipv4: use iph_set_totlen in skbuff_setattr Xin Long
2023-01-28 15:58 ` [PATCHv4 net-next 07/10] ipvlan: use skb_ip_totlen in ipvlan_get_L3_hdr Xin Long
2023-01-28 15:58 ` [PATCHv4 net-next 08/10] packet: add TP_STATUS_GSO_TCP for tp_status Xin Long
2023-02-01 15:32   ` David Ahern
2023-01-28 15:58 ` [PATCHv4 net-next 09/10] net: add gso_ipv4_max_size and gro_ipv4_max_size per device Xin Long
2023-01-31 14:59   ` Paolo Abeni
2023-01-31 17:55     ` Xin Long
2023-02-01 15:36   ` David Ahern
2023-01-28 15:58 ` [PATCHv4 net-next 10/10] net: add support for ipv4 big tcp Xin Long
2023-02-01 15:38   ` David Ahern
2023-02-02  9:24   ` [PATCHv4 net-next 10/10] net: add support for ipv4 big tcp: manual merge Matthieu Baerts
2023-02-01  8:53 ` [PATCHv4 net-next 00/10] net: support ipv4 big tcp Eric Dumazet
2023-02-01 15:39 ` David Ahern
2023-02-02  5: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=167531461888.3090.18277263241067373566.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=aconole@redhat$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dsahern@gmail$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=fw@strlen$(echo .)de \
    --cc=gnault@redhat$(echo .)com \
    --cc=i.maximets@ovn$(echo .)org \
    --cc=jhs@mojatatu$(echo .)com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=kuba@kernel$(echo .)org \
    --cc=lucien.xin@gmail$(echo .)com \
    --cc=maheshb@google$(echo .)com \
    --cc=marcelo.leitner@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=pablo@netfilter$(echo .)org \
    --cc=paul@paul-moore$(echo .)com \
    --cc=pshelar@ovn$(echo .)org \
    --cc=razor@blackwall$(echo .)org \
    --cc=roopa@nvidia$(echo .)com \
    --cc=xiyou.wangcong@gmail$(echo .)com \
    --cc=yoshfuji@linux-ipv6$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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