From: David Miller <davem@davemloft.net>
To: rohitm@chelsio.com
Cc: borisp@mellanox.com, netdev@vger.kernel.org,
herbert@gondor.apana.org.au, kuba@kernel.org, secdev@chelsio.com,
varun@chelsio.com
Subject: Re: [PATCH net-next v4 0/6] cxgb4/chcr: ktls tx ofld support on T6 adapter
Date: Sun, 08 Mar 2020 21:16:41 -0700 (PDT) [thread overview]
Message-ID: <20200308.211641.1162682781638307360.davem@davemloft.net> (raw)
In-Reply-To: <20200307143608.13109-1-rohitm@chelsio.com>
From: Rohit Maheshwari <rohitm@chelsio.com>
Date: Sat, 7 Mar 2020 20:06:02 +0530
> This series of patches add support for kernel tls offload in Tx direction,
> over Chelsio T6 NICs. SKBs marked as decrypted will be treated as tls plain
> text packets and then offloaded to encrypt using network device (chelsio T6
> adapter).
>
> This series is broken down as follows:
>
> Patch 1 defines a new macro and registers tls_dev_add and tls_dev_del
> callbacks. When tls_dev_add gets called we send a connection request to
> our hardware and to make HW understand about tls offload. Its a partial
> connection setup and only ipv4 part is done.
>
> Patch 2 handles the HW response of the connection request and then we
> request to update TCB and handle it's HW response as well. Also we save
> crypto key locally. Only supporting TLS_CIPHER_AES_GCM_128_KEY_SIZE.
>
> Patch 3 handles tls marked skbs (decrypted bit set) and sends it to ULD for
> crypto handling. This code has a minimal portion of tx handler, to handle
> only one complete record per skb.
>
> Patch 4 hanldes partial end part of records. Also added logic to handle
> multiple records in one single skb. It also adds support to send out tcp
> option(/s) if exists in skb. If a record is partial but has end part of a
> record, we'll fetch complete record and then only send it to HW to generate
> HASH on complete record.
>
> Patch 5 handles partial first or middle part of record, it uses AES_CTR to
> encrypt the partial record. If we are trying to send middle record, it's
> start should be 16 byte aligned, so we'll fetch few earlier bytes from the
> record and then send it to HW for encryption.
>
> Patch 6 enables ipv6 support and also includes ktls startistics.
>
> v1->v2:
> - mark tcb state to close in tls_dev_del.
> - u_ctx is now picked from adapter structure.
> - clear atid in case of failure.
> - corrected ULP_CRYPTO_KTLS_INLINE value.
> - optimized tcb update using control queue.
> - state machine handling when earlier states received.
> - chcr_write_cpl_set_tcb_ulp function is shifted to patch3.
> - un-necessary updating left variable.
>
> v2->v3:
> - add empty line after variable declaration.
> - local variable declaration in reverse christmas tree ordering.
>
> v3->v4:
> - replaced kfree_skb with dev_kfree_skb_any.
> - corrected error message reported by kbuild test robot <lkp@intel.com>
> - mss calculation logic.
> - correct place for Alloc skb check.
> - Replaced atomic_t with atomic64_t
> - added few more statistics counters.
Series applied, thank you.
prev parent reply other threads:[~2020-03-09 4:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 14:36 [PATCH net-next v4 0/6] cxgb4/chcr: ktls tx ofld support on T6 adapter Rohit Maheshwari
2020-03-07 14:36 ` [PATCH net-next v4 1/6] cxgb4/chcr : Register to tls add and del callback Rohit Maheshwari
2020-03-09 23:05 ` Jakub Kicinski
2020-03-09 23:10 ` Jakub Kicinski
2020-03-10 2:34 ` Herbert Xu
2020-03-10 5:32 ` rohit maheshwari
2020-03-07 14:36 ` [PATCH net-next v4 2/6] cxgb4/chcr: Save tx keys and handle HW response Rohit Maheshwari
2020-03-07 14:36 ` [PATCH net-next v4 3/6] cxgb4/chcr: complete record tx handling Rohit Maheshwari
2020-03-07 14:36 ` [PATCH net-next v4 4/6] chcr: handle partial end part of a record Rohit Maheshwari
2020-03-07 14:36 ` [PATCH net-next v4 5/6] chcr: Handle first or middle part of record Rohit Maheshwari
2020-03-07 14:36 ` [PATCH net-next v4 6/6] cxgb4/chcr: Add ipv6 support and statistics Rohit Maheshwari
2020-03-09 23:00 ` Jakub Kicinski
2020-03-10 5:37 ` rohit maheshwari
2020-03-09 4:16 ` David Miller [this message]
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=20200308.211641.1162682781638307360.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=borisp@mellanox.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rohitm@chelsio.com \
--cc=secdev@chelsio.com \
--cc=varun@chelsio.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