From: Atul Gupta <atul.gupta@chelsio.com>
To: davejwatson@fb.com, davem@davemloft.net, herbert@gondor.apana.org.au
Cc: sd@queasysnail.net, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, ganeshgr@chelsio.com
Subject: [Crypto v5 01/12] tls: tls_device struct to register TLS drivers
Date: Thu, 15 Feb 2018 12:24:43 +0530 [thread overview]
Message-ID: <1518677694-28448-2-git-send-email-atul.gupta@chelsio.com> (raw)
In-Reply-To: <1518677694-28448-1-git-send-email-atul.gupta@chelsio.com>
tls_device structure to register Inline TLS drivers
with net/tls
Signed-off-by: Atul Gupta <atul.gupta@chelsio.com>
---
include/net/tls.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/include/net/tls.h b/include/net/tls.h
index 936cfc5..6b64510 100644
--- a/include/net/tls.h
+++ b/include/net/tls.h
@@ -55,6 +55,28 @@
#define TLS_AAD_SPACE_SIZE 13
+#define TLS_DEVICE_NAME_MAX 32
+
+enum {
+ TLS_BASE_TX,
+ TLS_SW_TX,
+ TLS_FULL_HW, /* TLS record processed Inline */
+ TLS_NUM_CONFIG,
+};
+extern struct proto tls_prots[TLS_NUM_CONFIG];
+
+struct tls_device {
+ char name[TLS_DEVICE_NAME_MAX];
+ struct list_head dev_list;
+
+ /* netdev present in registered inline tls driver */
+ int (*netdev)(struct tls_device *device,
+ struct net_device *netdev);
+ int (*feature)(struct tls_device *device);
+ int (*hash)(struct tls_device *device, struct sock *sk);
+ void (*unhash)(struct tls_device *device, struct sock *sk);
+};
+
struct tls_sw_context {
struct crypto_aead *aead_send;
@@ -254,5 +276,7 @@ static inline struct tls_offload_context *tls_offload_ctx(
int tls_proccess_cmsg(struct sock *sk, struct msghdr *msg,
unsigned char *record_type);
+void tls_register_device(struct tls_device *device);
+void tls_unregister_device(struct tls_device *device);
#endif /* _TLS_OFFLOAD_H */
--
1.8.3.1
next prev parent reply other threads:[~2018-02-15 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 6:54 [Crypto v5 00/12] Chelsio Inline TLS Atul Gupta
2018-02-15 6:54 ` Atul Gupta [this message]
2018-02-15 6:54 ` [Crypto v5 02/12] ethtool: feature for Inline TLS in HW Atul Gupta
2018-02-15 6:54 ` [Crypto v5 03/12] support for inline tls Atul Gupta
2018-02-15 15:51 ` Dave Watson
2018-02-15 16:10 ` Atul Gupta
2018-02-15 16:26 ` Dave Watson
2018-02-15 16:31 ` Atul Gupta
2018-02-15 6:54 ` [Crypto v5 04/12] chtls: structure and macro definiton Atul Gupta
2018-02-15 6:54 ` [Crypto v5 05/12] cxgb4: Inline TLS FW Interface Atul Gupta
2018-02-15 6:54 ` [Crypto v5 06/12] cxgb4: LLD driver changes to enable TLS Atul Gupta
2018-02-15 6:54 ` [Crypto v5 07/12] chcr: Key Macro Atul Gupta
2018-02-15 6:54 ` [Crypto v5 08/12] chtls: Key program Atul Gupta
2018-02-15 6:54 ` [Crypto v5 09/12] chtls: CPL handler definition Atul Gupta
2018-02-15 6:54 ` [Crypto v5 10/12] chtls: Inline crypto request Tx/Rx Atul Gupta
2018-02-15 6:54 ` [Crypto v5 11/12] chtls: Register the chtls Inline TLS with net tls Atul Gupta
2018-02-15 6:54 ` [Crypto v5 12/12] Makefile Kconfig Atul Gupta
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=1518677694-28448-2-git-send-email-atul.gupta@chelsio.com \
--to=atul.gupta@chelsio.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).