From: Boris Pismenny <borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
ronye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
aviadye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: [RFC 0/2] IB/core: Add ESP Crypto Flow Steering support
Date: Thu, 20 Apr 2017 14:00:08 +0300 [thread overview]
Message-ID: <cover.1492685328.git.borisp@mellanox.com> (raw)
From: borisp <borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
The purpose of this RFC is to suggest an API for specifying
ESP crypto offload via flow steering. This API will allow users
to control the crypto offload functionality offered by new NICs,
such as Mellanox Innova IPsec.
Applications can request ESP encryption offload for transmission of
well-formed plaintext ESP packets, or decryption offload for
well-fromed ciphertext ESP packets. Packets are encrypted/decrypted
according to the direction of the flow.
In order to create an ESP crypto offload specification, the user has
to add it to a flow with the Security Association selectors.
borisp (2):
Introduce egress IB flow steering flag
IB/core: ESP AES-GCM crypto offload action
include/rdma/ib_verbs.h | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
--
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-04-20 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 11:00 Boris Pismenny [this message]
[not found] ` <cover.1492685328.git.borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-04-20 11:00 ` [RFC 1/2] Introduce egress IB flow steering flag Boris Pismenny
[not found] ` <8539540c4130ea91bbd128f2ec2845082d6000f8.1492685328.git.borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-04-20 17:48 ` Leon Romanovsky
[not found] ` <20170420174809.GS14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-20 18:31 ` Boris Pismenny
2017-04-20 11:00 ` [RFC 2/2] IB/core: ESP AES-GCM crypto offload action Boris Pismenny
2017-04-20 15:16 ` [RFC 0/2] IB/core: Add ESP Crypto Flow Steering support Steve Wise
2017-04-20 15:24 ` Boris Pismenny
[not found] ` <DB6PR05MB3176852A5F283F850E37DA70B01B0-HESHCvp+V+r3UGwzQMMk6dqRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-04-20 17:02 ` Jason Gunthorpe
[not found] ` <20170420170233.GA6275-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-04-20 17:15 ` Boris Pismenny
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.1492685328.git.borisp@mellanox.com \
--to=borisp-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=aviadye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=ronye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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