From: David Howells <dhowells@redhat.com>
To: Chuck Lever <cel@kernel.org>
Cc: dhowells@redhat.com, linux-nfs@vger.kernel.org,
netdev@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v3 0/5] Send RPC-on-TCP with one sock_sendmsg() call
Date: Wed, 26 Jul 2023 13:13:14 +0100 [thread overview]
Message-ID: <6565.1690373594@warthog.procyon.org.uk> (raw)
In-Reply-To: <168979108540.1905271.9720708849149797793.stgit@morisot.1015granger.net>
Chuck Lever <cel@kernel.org> wrote:
> After some discussion with David Howells at LSF/MM 2023, we arrived
> at a plan to use a single sock_sendmsg() call for transmitting an
> RPC message on socket-based transports. This is an initial part of
> the transition to support handling folios with file content, but it
> has scalability benefits as well.
>
> Initial performance benchmark results show 5-10% throughput gains
> with a fast link layer and a tmpfs export. I've added some other
> ideas to this series for further discussion -- these have also shown
> performance benefits in my testing.
I like it :-)
David
prev parent reply other threads:[~2023-07-26 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 18:30 [PATCH v3 0/5] Send RPC-on-TCP with one sock_sendmsg() call Chuck Lever
2023-07-19 18:31 ` [PATCH v3 1/5] SUNRPC: Convert svc_tcp_sendmsg to use bio_vecs directly Chuck Lever
2023-07-26 12:13 ` David Howells
2023-07-19 18:31 ` [PATCH v3 2/5] SUNRPC: Send RPC message on TCP with a single sock_sendmsg() call Chuck Lever
2023-07-24 9:58 ` David Howells
2023-07-24 13:27 ` Chuck Lever
2023-07-26 12:13 ` David Howells
2023-07-19 18:31 ` [PATCH v3 3/5] SUNRPC: Convert svc_udp_sendto() to use the per-socket bio_vec array Chuck Lever
2023-07-26 12:15 ` David Howells
2023-07-26 13:11 ` Chuck Lever
2023-07-19 18:31 ` [PATCH v3 4/5] SUNRPC: Revert e0a912e8ddba Chuck Lever
2023-07-26 12:14 ` David Howells
2023-07-19 18:31 ` [PATCH v3 5/5] SUNRPC: Reduce thread wake-up rate when receiving large RPC messages Chuck Lever
2023-07-26 12:13 ` David Howells [this message]
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=6565.1690373594@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.