From: David Ahern <dsahern@gmail•com>
To: Xin Long <lucien.xin@gmail•com>, network dev <netdev@vger•kernel.org>
Cc: davem@davemloft•net, kuba@kernel•org,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
Pravin B Shelar <pshelar@ovn•org>,
Jamal Hadi Salim <jhs@mojatatu•com>,
Cong Wang <xiyou.wangcong@gmail•com>,
Jiri Pirko <jiri@resnulli•us>,
Pablo Neira Ayuso <pablo@netfilter•org>,
Florian Westphal <fw@strlen•de>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>,
Ilya Maximets <i.maximets@ovn•org>,
Aaron Conole <aconole@redhat•com>,
Roopa Prabhu <roopa@nvidia•com>,
Nikolay Aleksandrov <razor@blackwall•org>,
Mahesh Bandewar <maheshb@google•com>,
Paul Moore <paul@paul-moore•com>,
Guillaume Nault <gnault@redhat•com>
Subject: Re: [PATCHv4 net-next 08/10] packet: add TP_STATUS_GSO_TCP for tp_status
Date: Wed, 1 Feb 2023 08:32:16 -0700 [thread overview]
Message-ID: <8e84db42-0774-43ed-9293-e80297ece7b4@gmail.com> (raw)
In-Reply-To: <0436a569c630a93e7abeedaa7ceccfc369f73c39.1674921359.git.lucien.xin@gmail.com>
On 1/28/23 8:58 AM, Xin Long wrote:
> Introduce TP_STATUS_GSO_TCP tp_status flag to tell the af_packet user
> that this is a TCP GSO packet. When parsing IPv4 BIG TCP packets in
> tcpdump/libpcap, it can use tp_len as the IPv4 packet len when this
> flag is set, as iph tot_len is set to 0 for IPv4 BIG TCP packets.
>
> Signed-off-by: Xin Long <lucien.xin@gmail•com>
> ---
> include/uapi/linux/if_packet.h | 1 +
> net/packet/af_packet.c | 4 ++++
> 2 files changed, 5 insertions(+)
>
Reviewed-by: David Ahern <dsahern@kernel•org>
next prev parent reply other threads:[~2023-02-01 15:32 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 [this message]
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
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=8e84db42-0774-43ed-9293-e80297ece7b4@gmail.com \
--to=dsahern@gmail$(echo .)com \
--cc=aconole@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--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