All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>,
	David Ahern <dsahern@gmail.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	"David S . Miller" <davem@davemloft.net>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	netdev@vger.kernel.org, Raed Salem <raeds@nvidia.com>,
	ipsec-devel <devel@linux-ipsec.org>
Subject: [PATCH iproute2=next 0/4] Add new IPsec offload type
Date: Tue, 10 May 2022 13:49:04 +0300	[thread overview]
Message-ID: <cover.1652179360.git.leonro@nvidia.com> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

Extend ip tool to support new IPsec offload mode.
Followup of the recently sent series to XFRM core.
https://lore.kernel.org/all/cover.1652176932.git.leonro@nvidia.com

Leon Romanovsky (4):
  Update kernel headers
  xfrm: prepare state offload logic to set mode
  xfrm: add full offload mode to xfrm state
  xfrm: add an interface to offload policy

 include/uapi/linux/xfrm.h |  1 +
 ip/ipxfrm.c               | 16 +++++++++----
 ip/xfrm.h                 |  4 ++--
 ip/xfrm_monitor.c         |  2 +-
 ip/xfrm_policy.c          | 26 +++++++++++++++++++++
 ip/xfrm_state.c           | 49 +++++++++++++++++++++++++--------------
 man/man8/ip-xfrm.8        | 14 +++++++++++
 7 files changed, 87 insertions(+), 25 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-05-10 10:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 10:49 Leon Romanovsky [this message]
2022-05-10 10:49 ` [PATCH iproute2-next 1/4] Update kernel headers Leon Romanovsky
2022-05-10 10:49 ` [PATCH iproute2-next 2/4] xfrm: prepare state offload logic to set mode Leon Romanovsky
2022-05-10 10:49 ` [PATCH iproute2-next 3/4] xfrm: add full offload mode to xfrm state Leon Romanovsky
2022-05-10 10:49 ` [PATCH iproute2-next 4/4] xfrm: add an interface to offload policy Leon Romanovsky

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=cover.1652179360.git.leonro@nvidia.com \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devel@linux-ipsec.org \
    --cc=dsahern@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=leonro@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=raeds@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.