From: Stefano Brivio <sbrivio@redhat.com>
To: Atul Gupta <atul.gupta@chelsio.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
davejwatson@fb.com, sd@queasysnail.net,
linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
werner@chelsio.com, leedom@chelsio.com,
swise@opengridcomputing.com, indranil@chelsio.com,
ganeshgr@chelsio.com
Subject: Re: [PATCH v13 net-next 09/12] crypto: chtls - Inline TLS record Tx
Date: Tue, 27 Mar 2018 19:51:16 +0200 [thread overview]
Message-ID: <20180327195116.0ac14f7e@epycfail> (raw)
In-Reply-To: <1522172201-7629-10-git-send-email-atul.gupta@chelsio.com>
On Tue, 27 Mar 2018 23:06:38 +0530
Atul Gupta <atul.gupta@chelsio.com> wrote:
> +static u8 tcp_state_to_flowc_state(u8 state)
> +{
> + u8 ret = FW_FLOWC_MNEM_TCPSTATE_ESTABLISHED;
> +
> + switch (state) {
> + case TCP_ESTABLISHED:
> + ret = FW_FLOWC_MNEM_TCPSTATE_ESTABLISHED;
> + break;
> + case TCP_CLOSE_WAIT:
> + ret = FW_FLOWC_MNEM_TCPSTATE_CLOSEWAIT;
> + break;
> + case TCP_FIN_WAIT1:
> + ret = FW_FLOWC_MNEM_TCPSTATE_FINWAIT1;
> + break;
> + case TCP_CLOSING:
> + ret = FW_FLOWC_MNEM_TCPSTATE_CLOSING;
> + break;
> + case TCP_LAST_ACK:
> + ret = FW_FLOWC_MNEM_TCPSTATE_LASTACK;
> + break;
> + case TCP_FIN_WAIT2:
> + ret = FW_FLOWC_MNEM_TCPSTATE_FINWAIT2;
> + break;
Can't you just return those values right away instead?
> [...]
>
> +static u64 tlstx_seq_number(struct chtls_hws *hws)
> +{
> + return hws->tx_seq_no++;
> +}
The name of this function, as I also had commented earlier, is
misleading, because you are also incrementing the sequence number.
> [...]
>
> +static void mark_urg(struct tcp_sock *tp, int flags,
> + struct sk_buff *skb)
> +{
> + if (unlikely(flags & MSG_OOB)) {
> + tp->snd_up = tp->write_seq;
> + ULP_SKB_CB(skb)->flags = ULPCB_FLAG_URG |
> + ULPCB_FLAG_BARRIER |
> + ULPCB_FLAG_NO_APPEND |
> + ULPCB_FLAG_NEED_HDR;
Is this indentation the result of a previous 'if' clause which is now
gone?
> [...]
>
> +/*
> + * Returns true if a TCP socket is corked.
> + */
> +static int corked(const struct tcp_sock *tp, int flags)
> +{
> + return (flags & MSG_MORE) | (tp->nonagle & TCP_NAGLE_CORK);
I guess you meant || here. Shouldn't this be a bool?
> +}
> +
> +/*
> + * Returns true if a send should try to push new data.
> + */
> +static int send_should_push(struct sock *sk, int flags)
> +{
> + return should_push(sk) && !corked(tcp_sk(sk), flags);
> +}
If it returns true, I guess it should be a bool.
> [...]
--
Stefano
next prev parent reply other threads:[~2018-03-27 17:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 17:36 [PATCH v13 net-next 00/12] Chelsio Inline TLS Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 01/12] tls: support for Inline tls record Atul Gupta
2018-03-27 18:23 ` Stefano Brivio
2018-03-28 4:28 ` Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 02/12] ethtool: enable Inline TLS in HW Atul Gupta
2018-03-27 20:44 ` Sabrina Dubroca
2018-03-28 3:36 ` [SPAMMY (6.9)]Re: " Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 03/12] cxgb4: Inline TLS FW Interface Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 04/12] cxgb4: LLD driver changes to support TLS Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 05/12] crypto: chcr - Inline TLS Key Macros Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 06/12] crypto: chtls - structure and macro for Inline TLS Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 07/12] crypto: chtls - Program the TLS session Key Atul Gupta
2018-03-27 17:41 ` Stefano Brivio
2018-03-27 18:16 ` Stefano Brivio
2018-03-27 17:36 ` [PATCH v13 net-next 08/12] crypto : chtls - CPL handler definition Atul Gupta
2018-03-27 17:42 ` Stefano Brivio
2018-03-28 3:39 ` Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 09/12] crypto: chtls - Inline TLS record Tx Atul Gupta
2018-03-27 17:41 ` Stefano Brivio
2018-03-27 17:51 ` Stefano Brivio [this message]
2018-03-27 17:36 ` [PATCH v13 net-next 10/12] crypto: chtls - Inline TLS record Rx Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 11/12] crypto: chtls - Register chtls with net tls Atul Gupta
2018-03-27 17:36 ` [PATCH v13 net-next 12/12] crypto: chtls - 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=20180327195116.0ac14f7e@epycfail \
--to=sbrivio@redhat.com \
--cc=atul.gupta@chelsio.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=indranil@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=swise@opengridcomputing.com \
--cc=werner@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;
as well as URLs for NNTP newsgroup(s).