From: Paolo Abeni <pabeni@redhat.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: sunyiqi <sunyiqixm@gmail.com>,
edumazet@google.com, davem@davemloft.net, dsahern@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: remove release/lock_sock in tcp_splice_read
Date: Thu, 15 Aug 2024 13:22:54 +0200 [thread overview]
Message-ID: <dc46f9de-641e-4b38-8661-4efd4859f49b@redhat.com> (raw)
In-Reply-To: <CAL+tcoAiOwWEsbkqSJ3kpwLxd8seBBUOAODeBideFdQYV7LfWg@mail.gmail.com>
On 8/15/24 12:55, Jason Xing wrote:
> On Thu, Aug 15, 2024 at 6:40 PM Paolo Abeni <pabeni@redhat.com> wrote:
> [...]
>>> - release_sock(sk);
>>> - lock_sock(sk);
>>
>> This is needed to flush the sk backlog.
>>
>> Somewhat related, I think we could replace the pair with sk_flush_backlog().
>>
>
> Do you think we could do this like the following commit:
>
> commit d41a69f1d390fa3f2546498103cdcd78b30676ff
> Author: Eric Dumazet <edumazet@google.com>
> Date: Fri Apr 29 14:16:53 2016 -0700
>
> tcp: make tcp_sendmsg() aware of socket backlog
>
> Large sendmsg()/write() hold socket lock for the duration of the call,
> unless sk->sk_sndbuf limit is hit. This is bad because incoming packets
> are parked into socket backlog for a long time. >
> ?
Yep. To be more accurate I was looking at commit
93afcfd1db35882921b2521a637c78755c27b02c
In any case this should be unrelated from the supposed issue.
Cheers,
Paolo
next prev parent reply other threads:[~2024-08-15 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 8:43 sunyiqi
2024-08-15 10:00 ` Paolo Abeni
2024-08-15 10:55 ` Jason Xing
2024-08-15 11:22 ` Paolo Abeni [this message]
2024-08-15 11:34 ` Jason Xing
2024-08-15 10:48 ` Jason Xing
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=dc46f9de-641e-4b38-8661-4efd4859f49b@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sunyiqixm@gmail.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
all inboxes | Powered by JetHome®