From: Pavel Begunkov <asml.silence@gmail.com>
To: netdev@vger.kernel.org, edumazet@google.com, davem@davemloft.net,
dsahern@kernel.org, pabeni@redhat.com, kuba@kernel.org
Cc: Pavel Begunkov <asml.silence@gmail.com>
Subject: [PATCH net-next 0/2] TCP splice improvements
Date: Fri, 19 May 2023 14:33:03 +0100 [thread overview]
Message-ID: <cover.1684501922.git.asml.silence@gmail.com> (raw)
The main part is in Patch 1, which optimises locking for successful
blocking TCP splice read, following with a clean up in Patch 2.
Pavel Begunkov (2):
net/tcp: optimise locking for blocking splice
net/tcp: optimise non error splice paths
net/ipv4/tcp.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
--
2.40.0
next reply other threads:[~2023-05-19 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 13:33 Pavel Begunkov [this message]
2023-05-19 13:33 ` [PATCH net-next 1/2] net/tcp: optimise locking for blocking splice Pavel Begunkov
2023-05-23 13:52 ` Paolo Abeni
2023-05-24 12:51 ` Pavel Begunkov
2023-06-19 9:27 ` Pavel Begunkov
2023-06-19 10:59 ` Eric Dumazet
2023-06-23 13:42 ` Pavel Begunkov
2023-05-19 13:33 ` [PATCH net-next 2/2] net/tcp: optimise non error splice paths Pavel Begunkov
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=cover.1684501922.git.asml.silence@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).