Netdev List
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: antony.antony@secunet.com,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org, devel@linux-ipsec.org,
	Leon Romanovsky <leon@kernel.org>,
	Eyal Birger <eyal.birger@gmail.com>
Subject: Re: [PATCH ipsec-next v5] xfrm: Add Direction to the SA in or out
Date: Thu, 4 Apr 2024 16:08:42 +0200	[thread overview]
Message-ID: <13307e0d-11c8-4530-8182-37ecb2f8b8a3@6wind.com> (raw)
In-Reply-To: <0baa206a7e9c6257826504e1f57103a84ce17b41.1712219452.git.antony.antony@secunet.com>

Le 04/04/2024 à 10:32, Antony Antony a écrit :
> This patch introduces the 'dir' attribute, 'in' or 'out', to the
> xfrm_state, SA, enhancing usability by delineating the scope of values
> based on direction. An input SA will now exclusively encompass values
> pertinent to input, effectively segregating them from output-related
> values. This change aims to streamline the configuration process and
> improve the overall clarity of SA attributes.
> 
> This feature sets the groundwork for future patches, including
> the upcoming IP-TFS patch. Additionally, the 'dir' attribute can
> serve purely informational purposes.
> It currently validates the XFRM_OFFLOAD_INBOUND flag for hardware
> offload capabilities.
Frankly, it's a poor API. It will be more confusing than useful.
This informational attribute could be wrong, there is no check.
Please consider use cases of people that don't do offload.

The kernel could accept this attribute only in case of offload. This could be
relaxed later if needed. With no check at all, nothing could be done later, once
it's in the uapi.


Regards,
Nicolas

  reply	other threads:[~2024-04-04 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  8:32 [PATCH ipsec-next v5] xfrm: Add Direction to the SA in or out Antony Antony
2024-04-04 14:08 ` Nicolas Dichtel [this message]
2024-04-05 12:29   ` Antony Antony
2024-04-05 13:29     ` Nicolas Dichtel
2024-04-06 12:39   ` [devel-ipsec] " Christian Hopps

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=13307e0d-11c8-4530-8182-37ecb2f8b8a3@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=antony.antony@secunet.com \
    --cc=devel@linux-ipsec.org \
    --cc=eyal.birger@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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