From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
David Ahern <dsahern@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/6] splice, net: Some miscellaneous MSG_SPLICE_PAGES changes
Date: Fri, 9 Jun 2023 11:02:15 +0100 [thread overview]
Message-ID: <20230609100221.2620633-1-dhowells@redhat.com> (raw)
Now that the splice_to_socket() has been rewritten so that nothing now uses
the ->sendpage() file op[1], some further changes can be made, so here are
some miscellaneous changes that can now be done.
(1) Remove the ->sendpage() file op.
(2) Remove hash_sendpage*() from AF_ALG.
(3) Make sunrpc send multiple pages in single sendmsg() call rather than
calling sendpage() in TCP (or maybe TLS).
(4) Make tcp_bpf_sendpage() a wrapper around tcp_bpf_sendmsg().
(5) Make AF_KCM use sendmsg() when calling down to TCP and then make it
send entire fragment lists in single sendmsg calls.
I've pushed the patches here also:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=sendpage-3-misc
David
Link: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=fd5f4d7da29218485153fd8b4c08da7fc130c79f [1]
David Howells (6):
Remove file->f_op->sendpage
algif: Remove hash_sendpage*()
sunrpc: Use sendmsg(MSG_SPLICE_PAGES) rather then sendpage
tcp_bpf: Make tcp_bpf_sendpage() go through
tcp_bpf_sendmsg(MSG_SPLICE_PAGES)
kcm: Use sendmsg(MSG_SPLICE_PAGES) rather then sendpage
kcm: Send multiple frags in one sendmsg()
crypto/algif_hash.c | 66 --------------------
include/linux/fs.h | 1 -
include/linux/sunrpc/svc.h | 11 ++--
include/net/kcm.h | 2 +-
net/ipv4/tcp_bpf.c | 49 +++------------
net/kcm/kcmsock.c | 120 ++++++++++++++++---------------------
net/sunrpc/svcsock.c | 38 ++++--------
7 files changed, 77 insertions(+), 210 deletions(-)
next reply other threads:[~2023-06-09 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 10:02 David Howells [this message]
2023-06-09 10:02 ` [PATCH net-next 1/6] Remove file->f_op->sendpage David Howells
2023-06-09 10:02 ` [PATCH net-next 2/6] algif: Remove hash_sendpage*() David Howells
2023-06-09 10:02 ` [PATCH net-next 3/6] sunrpc: Use sendmsg(MSG_SPLICE_PAGES) rather then sendpage David Howells
2023-08-11 22:50 ` Jeff Layton
2023-08-11 23:07 ` Jeff Layton
2023-08-12 11:45 ` Jeff Layton
2023-06-09 10:02 ` [PATCH net-next 4/6] tcp_bpf: Make tcp_bpf_sendpage() go through tcp_bpf_sendmsg(MSG_SPLICE_PAGES) David Howells
2023-06-09 10:02 ` [PATCH net-next 5/6] kcm: Use sendmsg(MSG_SPLICE_PAGES) rather then sendpage David Howells
2023-06-09 10:02 ` [PATCH net-next 6/6] kcm: Send multiple frags in one sendmsg() David Howells
2023-06-13 5:10 ` [PATCH net-next 0/6] splice, net: Some miscellaneous MSG_SPLICE_PAGES changes 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=20230609100221.2620633-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=willy@infradead.org \
/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).