From: Sabrina Dubroca <sd@queasysnail.net>
To: Atul Gupta <atul.gupta@chelsio.com>
Cc: davejwatson@fb.com, davem@davemloft.net,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, ganeshgr@chelsio.com
Subject: Re: [PATCH v9 crypto 02/12] ethtool: enable Inline TLS in HW
Date: Wed, 7 Mar 2018 13:35:30 +0100 [thread overview]
Message-ID: <20180307123530.GC20949@bistromath.localdomain> (raw)
In-Reply-To: <1520350642-11852-1-git-send-email-atul.gupta@chelsio.com>
Since you're saying the driver supports offloading TLS records to the
HW, why not call the feature "record offloading"? With, for example,
NETIF_F_HW_TLS_RECORD as the feature, and maybe "tls-hw-record" for
the ethtool string. This "Inline TLS" name sounds rather like
marketing to me.
2018-03-06, 21:07:22 +0530, Atul Gupta wrote:
> Signed-off-by: Atul Gupta <atul.gupta@chelsio.com>
There should be a description here of what the feature covers, so that
other drivers can decide if it matches what their HW supports.
--
Sabrina
next prev parent reply other threads:[~2018-03-07 12:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 15:35 [PATCH v9 crypto 00/12] Chelsio Inline TLS Atul Gupta
2018-03-06 15:36 ` [PATCH v9 crypto 01/12] tls: tls_device struct to register TLS drivers Atul Gupta
2018-03-07 10:16 ` Sabrina Dubroca
2018-03-07 11:21 ` Atul Gupta
2018-03-06 15:37 ` [PATCH v9 crypto 02/12] ethtool: enable Inline TLS in HW Atul Gupta
2018-03-07 12:35 ` Sabrina Dubroca [this message]
2018-03-07 12:44 ` Atul Gupta
2018-03-06 15:38 ` [PATCH v9 crypto 00/12] Chelsio Inline TLS Vakul Garg
2018-03-06 15:45 ` Atul Gupta
2018-03-07 10:23 ` Sabrina Dubroca
2018-03-07 11:26 ` Atul Gupta
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 15:39 [PATCH v9 crypto 04/12] chtls: structure and macro definiton Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 05/12] cxgb4: Inline TLS FW Interface Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 06/12] cxgb4: LLD driver changes to enable TLS Atul Gupta
2018-03-07 12:59 ` Sabrina Dubroca
2018-03-08 8:58 ` Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 07/12] chcr: Key Macro Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 08/12] chtls: Key program Atul Gupta
2018-03-07 15:05 ` Sabrina Dubroca
2018-03-08 11:18 ` Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 09/12] chtls: CPL handler definition Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 10/12] chtls: Inline crypto request Tx/Rx Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 11/12] chtls: Register chtls Inline TLS with net tls Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 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=20180307123530.GC20949@bistromath.localdomain \
--to=sd@queasysnail.net \
--cc=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 \
/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).