From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com
Cc: davem@davemloft.net, rds-devel@oss.oracle.com,
sowmini.varadhan@oracle.com, santosh.shilimkar@oracle.com
Subject: [PATCH RESEND V3 net-next 0/3] RDS: optimized notification for zerocopy completion
Date: Tue, 27 Feb 2018 09:08:01 -0800 [thread overview]
Message-ID: <cover.1519600399.git.sowmini.varadhan@oracle.com> (raw)
Resending with acked-by additions: previous attempt does not show
up in Patchwork.
RDS applications use predominantly request-response, transacation
based IPC, so that ingress and egress traffic are well-balanced,
and it is possible/desirable to reduce system-call overhead by
piggybacking the notifications for zerocopy completion response
with data.
Moreover, it has been pointed out that socket functions block
if sk_err is non-zero, thus if the RDS code does not plan/need
to use sk_error_queue path for completion notification, it
is preferable to remove the sk_errror_queue related paths in
RDS.
Both of these goals are implemented in this series.
v2: removed sk_error_queue support
v3: incorporated additional code review comments (details in each patch)
Sowmini Varadhan (3):
selftests/net: revert the zerocopy Rx path for PF_RDS
rds: deliver zerocopy completion notification with data
selftests/net: reap zerocopy completions passed up as ancillary data.
include/uapi/linux/errqueue.h | 2 -
include/uapi/linux/rds.h | 7 ++
net/rds/af_rds.c | 7 +-
net/rds/message.c | 38 ++++-----
net/rds/rds.h | 2 +
net/rds/recv.c | 31 +++++++-
tools/testing/selftests/net/msg_zerocopy.c | 120 ++++++++++++----------------
7 files changed, 111 insertions(+), 96 deletions(-)
next reply other threads:[~2018-02-27 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 17:08 Sowmini Varadhan [this message]
2018-02-26 16:56 ` [PATCH V3 net-next 0/3] RDS: optimized notification for zerocopy completion Willem de Bruijn
2018-02-27 17:08 ` [PATCH RESEND V3 net-next 1/3] selftests/net: revert the zerocopy Rx path for PF_RDS Sowmini Varadhan
2018-02-27 17:08 ` [PATCH RESEND V3 net-next 2/3] rds: deliver zerocopy completion notification with data Sowmini Varadhan
2018-02-26 17:07 ` [PATCH " Santosh Shilimkar
2018-02-26 17:11 ` Sowmini Varadhan
2018-02-26 17:13 ` David Miller
2018-02-26 17:15 ` Santosh Shilimkar
2018-02-27 17:08 ` [PATCH RESEND V3 net-next 3/3] selftests/net: reap zerocopy completions passed up as ancillary data Sowmini Varadhan
-- strict thread matches above, loose matches on Subject: below --
2018-02-27 17:52 [PATCH RESEND V3 net-next 0/3] RDS: optimized notification for zerocopy completion Sowmini Varadhan
2018-02-27 19:19 ` David Miller
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.1519600399.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=willemdebruijn.kernel@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;
as well as URLs for NNTP newsgroup(s).