netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Hopps <chopps@chopps.org>
To: devel@linux-ipsec.org
Cc: 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>,
	Christian Hopps <chopps@chopps.org>,
	Christian Hopps <chopps@labn.net>
Subject: [PATCH ipsec-next v13 01/15] xfrm: config: add CONFIG_XFRM_IPTFS
Date: Tue,  5 Nov 2024 03:37:45 -0500	[thread overview]
Message-ID: <20241105083759.2172771-2-chopps@chopps.org> (raw)
In-Reply-To: <20241105083759.2172771-1-chopps@chopps.org>

From: Christian Hopps <chopps@labn.net>

Add new Kconfig option to enable IP-TFS (RFC9347) functionality.

Signed-off-by: Christian Hopps <chopps@labn.net>
---
 net/xfrm/Kconfig | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/net/xfrm/Kconfig b/net/xfrm/Kconfig
index d7b16f2c23e9..f0157702718f 100644
--- a/net/xfrm/Kconfig
+++ b/net/xfrm/Kconfig
@@ -135,6 +135,22 @@ config NET_KEY_MIGRATE
 
 	  If unsure, say N.
 
+config XFRM_IPTFS
+	tristate "IPsec IP-TFS/AGGFRAG (RFC 9347) encapsulation support"
+	depends on XFRM
+	help
+	  Information on the IP-TFS/AGGFRAG encapsulation can be found
+	  in RFC 9347. 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.
+
+	  If unsure, say N.
+
 config XFRM_ESPINTCP
 	bool
 
-- 
2.47.0


  reply	other threads:[~2024-11-05  8:38 UTC|newest]

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

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=20241105083759.2172771-2-chopps@chopps.org \
    --to=chopps@chopps.org \
    --cc=antony@phenome.org \
    --cc=chopps@labn.net \
    --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).