netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antony Antony <antony.antony@secunet.com>
To: Christian Hopps <chopps@chopps.org>
Cc: <devel@linux-ipsec.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	<netdev@vger.kernel.org>, Florian Westphal <fw@strlen.de>,
	Sabrina Dubroca <sd@queasysnail.net>,
	Simon Horman <horms@kernel.org>,
	Antony Antony <antony@phenome.org>
Subject: Re: [devel-ipsec] [PATCH ipsec-next v14 00/15] Add IP-TFS mode to xfrm
Date: Tue, 19 Nov 2024 13:10:26 +0100	[thread overview]
Message-ID: <ZzyAMsShJSt8nyZU@moon.secunet.de> (raw)
In-Reply-To: <20241114070713.3718740-1-chopps@chopps.org>

On Thu, Nov 14, 2024 at 02:06:57 -0500, Christian Hopps via Devel wrote:
> * Summary of Changes:
> 
> This patchset adds a new xfrm mode implementing on-demand IP-TFS. IP-TFS
> (AggFrag encapsulation) has been standardized in RFC9347.
> 
>   Link: https://www.rfc-editor.org/rfc/rfc9347.txt
> 
> This feature supports demand driven (i.e., non-constant send rate)
> IP-TFS to take advantage of the AGGFRAG ESP payload encapsulation. This
> payload type supports aggregation and fragmentation of the inner IP
> packet stream which in turn yields higher small-packet bandwidth as well
> as reducing MTU/PMTU issues. Congestion control is unimplementated as
> the send rate is demand driven rather than constant.
> 
> In order to allow loading this fucntionality as a module a set of
> callbacks xfrm_mode_cbs has been added to xfrm as well.
> 
> Patchset Structure:
> -------------------
> 
> The first 5 commits are changes to the net and xfrm infrastructure to
> support the callbacks as well as more generic IP-TFS additions that
> may be used outside the actual IP-TFS implementation.
> 
>   - xfrm: config: add CONFIG_XFRM_IPTFS
>   - include: uapi: protocol number and packet structs for AGGFRAG in ESP
>   - xfrm: netlink: add config (netlink) options
>   - xfrm: add mode_cbs module functionality
>   - xfrm: add generic iptfs defines and functionality
> 
> The last 10 commits constitute the IP-TFS implementation constructed in
> layers to make review easier. The first 9 commits all apply to a single
> file `net/xfrm/xfrm_iptfs.c`, the last commit adds a new tracepoint
> header file along with the use of these new tracepoint calls.
> 
>   - xfrm: iptfs: add new iptfs xfrm mode impl
>   - xfrm: iptfs: add user packet (tunnel ingress) handling
>   - xfrm: iptfs: share page fragments of inner packets
>   - xfrm: iptfs: add fragmenting of larger than MTU user packets
>   - xfrm: iptfs: add basic receive packet (tunnel egress) handling
>   - xfrm: iptfs: handle received fragmented inner packets
>   - xfrm: iptfs: add reusing received skb for the tunnel egress packet
>   - xfrm: iptfs: add skb-fragment sharing code
>   - xfrm: iptfs: handle reordering of received packets
>   - xfrm: iptfs: add tracepoint functionality

I did several functional tests with the entire patch set.

Tested-by: Antony Antony <antony.antony@secunet.com>

Feel free to add this tag in the next re-base.

thanks,
-antony

  parent reply	other threads:[~2024-11-19 12:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14  7:06 [PATCH ipsec-next v14 00/15] Add IP-TFS mode to xfrm Christian Hopps
2024-11-14  7:06 ` [PATCH ipsec-next v14 01/15] xfrm: config: add CONFIG_XFRM_IPTFS Christian Hopps
2024-11-14  7:06 ` [PATCH ipsec-next v14 02/15] include: uapi: protocol number and packet structs for AGGFRAG in ESP Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 03/15] xfrm: netlink: add config (netlink) options Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 04/15] xfrm: add mode_cbs module functionality Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 05/15] xfrm: add generic iptfs defines and functionality Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 06/15] xfrm: iptfs: add new iptfs xfrm mode impl Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 07/15] xfrm: iptfs: add user packet (tunnel ingress) handling Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 08/15] xfrm: iptfs: share page fragments of inner packets Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 09/15] xfrm: iptfs: add fragmenting of larger than MTU user packets Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 10/15] xfrm: iptfs: add basic receive packet (tunnel egress) handling Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 11/15] xfrm: iptfs: handle received fragmented inner packets Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 12/15] xfrm: iptfs: add reusing received skb for the tunnel egress packet Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 13/15] xfrm: iptfs: add skb-fragment sharing code Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 14/15] xfrm: iptfs: handle reordering of received packets Christian Hopps
2024-11-14  7:07 ` [PATCH ipsec-next v14 15/15] xfrm: iptfs: add tracepoint functionality Christian Hopps
2024-11-19 12:10 ` Antony Antony [this message]
2024-12-09  9:23 ` [PATCH ipsec-next v14 00/15] Add IP-TFS mode to xfrm Steffen Klassert

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=ZzyAMsShJSt8nyZU@moon.secunet.de \
    --to=antony.antony@secunet.com \
    --cc=antony@phenome.org \
    --cc=chopps@chopps.org \
    --cc=devel@linux-ipsec.org \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --cc=steffen.klassert@secunet.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).