[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0e230fdf-6af6-926f-305e-2f34ac6a6812@suse.de>
Date: Mon, 3 Jul 2023 12:21:32 +0200
From: Hannes Reinecke <hare@...e.de>
To: Sagi Grimberg <sagi@...mberg.me>
Cc: Keith Busch <kbusch@...nel.org>, Christoph Hellwig <hch@....de>,
linux-nvme@...ts.infradead.org, Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH 4/5] net/tls: split tls_rx_reader_lock
On 7/3/23 12:06, Sagi Grimberg wrote:
>
>
> On 7/3/23 12:04, Hannes Reinecke wrote:
>> Split tls_rx_reader_{lock,unlock} into an 'acquire/release' and
>> the actual locking part.
>> With that we can use the tls_rx_reader_lock in situations where
>> the socket is already locked.
>>
>> Suggested-by: Sagi Grimberg <sagi@...mberg.me>
>> Signed-off-by: Hannes Reinecke <hare@...e.de>
>> ---
>> net/tls/tls_sw.c | 38 ++++++++++++++++++++++----------------
>> 1 file changed, 22 insertions(+), 16 deletions(-)
>>
>> diff --git a/net/tls/tls_sw.c b/net/tls/tls_sw.c
>> index 9aef45e870a5..d0636ea13009 100644
>> --- a/net/tls/tls_sw.c
>> +++ b/net/tls/tls_sw.c
>> @@ -1848,13 +1848,10 @@ tls_read_flush_backlog(struct sock *sk, struct
>> tls_prot_info *prot,
>> return sk_flush_backlog(sk);
>> }
>> -static int tls_rx_reader_lock(struct sock *sk, struct
>> tls_sw_context_rx *ctx,
>> - bool nonblock)
>> +static int tls_rx_reader_acquire(struct sock *sk, struct
>> tls_sw_context_rx *ctx,
>> + bool nonblock)
>
> Nit: I still think tls_rx_reader_enter/tls_rx_reader_exit are more
> appropriate names.
I don't mind either way, but I've interpreted the comments from Jakub
that he'd like this naming better.
Jakub?
Cheers,
Hannes
Powered by blists - more mailing lists