From: Pavel Begunkov <asml.silence@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
pabeni@redhat.com, kuba@kernel.org
Subject: Re: [PATCH net-next v2] net/tcp: optimise locking for blocking splice
Date: Fri, 23 Jun 2023 16:03:46 +0100 [thread overview]
Message-ID: <f3427348-41ee-e0bf-79b6-9ff5120e8110@gmail.com> (raw)
In-Reply-To: <CANn89i+fhE76=i2J0VFacQoOqqA_iJNLazjbcHFGpu4JA6+1BQ@mail.gmail.com>
On 6/23/23 15:17, Eric Dumazet wrote:
> On Fri, Jun 23, 2023 at 2:40 PM Pavel Begunkov <asml.silence@gmail.com> wrote:
>>
>> Even when tcp_splice_read() reads all it was asked for, for blocking
>> sockets it'll release and immediately regrab the socket lock, loop
>> around and break on the while check.
>>
>> Check tss.len right after we adjust it, and return if we're done.
>> That saves us one release_sock(); lock_sock(); pair per successful
>> blocking splice read.
>>
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
>> ---
>>
>> v2: go with Paolo's suggestion
>> aggressively shrink the patch
>>
>> net/ipv4/tcp.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
>> index 71b42eef9dbf..d56edc2c885f 100644
>> --- a/net/ipv4/tcp.c
>> +++ b/net/ipv4/tcp.c
>> @@ -839,7 +839,7 @@ ssize_t tcp_splice_read(struct socket *sock, loff_t *ppos,
>> tss.len -= ret;
>> spliced += ret;
>>
>> - if (!timeo)
>> + if (!tss.len || !timeo)
>> break;
>> release_sock(sk);
>> lock_sock(sk);
>
> SGTM, thanks.
>
> Reviewed-by: Eric Dumazet <edumazet@google.com>
>
> I wonder if the "release_sock();sock_lock();" could be replaced by
> sk_flush_backlog() anyway ?
> Or is there any other reason for this dance ?
Now as you mentioned, it definitely sounds like that. And the code
is 15 years old, perhaps nobody was paying attention.
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index 71b42eef9dbf527098963bc03deecf55042e2021..d03d38060944d63d2728a7bf90a5c117b7852d8b
> 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -841,8 +841,7 @@ ssize_t tcp_splice_read(struct socket *sock, loff_t *ppos,
>
> if (!timeo)
> break;
> - release_sock(sk);
> - lock_sock(sk);
> + sk_flush_backlog();
>
> if (sk->sk_err || sk->sk_state == TCP_CLOSE ||
> (sk->sk_shutdown & RCV_SHUTDOWN) ||
--
Pavel Begunkov
next prev parent reply other threads:[~2023-06-23 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 12:38 [PATCH net-next v2] net/tcp: optimise locking for blocking splice Pavel Begunkov
2023-06-23 14:17 ` Eric Dumazet
2023-06-23 15:03 ` Pavel Begunkov [this message]
2023-06-24 22:30 ` patchwork-bot+netdevbpf
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=f3427348-41ee-e0bf-79b6-9ff5120e8110@gmail.com \
--to=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).