From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
rds-devel@oss.oracle.com
Subject: Re: [PATCH V2 net-next 4/7] rds: support for zcopy completion notification
Date: Wed, 14 Feb 2018 13:39:35 -0800 [thread overview]
Message-ID: <4f85d732-f060-9510-6fdb-1458aa4cf435@oracle.com> (raw)
In-Reply-To: <20180214212524.GR11528@oracle.com>
On 2/14/2018 1:25 PM, Sowmini Varadhan wrote:
> On (02/14/18 13:10), Santosh Shilimkar wrote:
>>>>> RDS support true zero copy already with RDMA transport so some of
>>>>> this code can easily get confused.
>
> btw, another way to solve this is to have the RDMA code use the
> suffix "rdma" (which is what it really is) as needed.
>
And same breath,here zcopy is No message from user ;-)
ZCOPY is otherwise often tied with RDMA directly.
Renaming churns are not that useful and I definitely agree
with what Dave said if it was renaming change to the
existing code like what you are suggesting with 'rdma'
Anyways I don't want to contest this too much since I can
follow that code and know what each does and means :-)
The comment was long term readability perspective for
some one completely new reading the code and being able to
distinguish the different modes.
Regards,
Santosh
next prev parent reply other threads:[~2018-02-14 21:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 10:28 [PATCH V2 net-next 0/7] RDS: zerocopy support Sowmini Varadhan
2018-02-14 10:28 ` [PATCH V2 net-next 1/7] skbuff: export mm_[un]account_pinned_pages for other modules Sowmini Varadhan
2018-02-14 10:28 ` [PATCH V2 net-next 2/7] rds: hold a sock ref from rds_message to the rds_sock Sowmini Varadhan
2018-02-14 18:38 ` Santosh Shilimkar
2018-02-14 10:28 ` [PATCH V2 net-next 3/7] sock: permit SO_ZEROCOPY on PF_RDS socket Sowmini Varadhan
2018-02-14 10:28 ` [PATCH V2 net-next 4/7] rds: support for zcopy completion notification Sowmini Varadhan
2018-02-14 18:50 ` Santosh Shilimkar
2018-02-14 19:01 ` Sowmini Varadhan
2018-02-14 19:02 ` David Miller
2018-02-14 21:10 ` Santosh Shilimkar
2018-02-14 21:25 ` Sowmini Varadhan
2018-02-14 21:39 ` Santosh Shilimkar [this message]
2018-02-14 22:08 ` Santosh Shilimkar
2018-02-14 19:17 ` Santosh Shilimkar
2018-02-14 22:26 ` Willem de Bruijn
2018-02-15 0:19 ` Santosh Shilimkar
2018-02-15 0:12 ` Willem de Bruijn
2018-02-15 0:41 ` Willem de Bruijn
2018-02-15 12:03 ` Sowmini Varadhan
2018-02-15 16:35 ` Willem de Bruijn
2018-02-15 16:43 ` Sowmini Varadhan
2018-02-14 10:28 ` [PATCH V2 net-next 5/7] rds: zerocopy Tx support Sowmini Varadhan
2018-02-14 19:10 ` Santosh Shilimkar
2018-02-14 19:49 ` Sowmini Varadhan
2018-02-14 21:14 ` Santosh Shilimkar
2018-02-14 23:48 ` Willem de Bruijn
2018-02-15 0:09 ` Sowmini Varadhan
2018-02-15 0:15 ` Willem de Bruijn
2018-02-14 10:28 ` [PATCH V2 net-next 6/7] selftests/net: add support for PF_RDS sockets Sowmini Varadhan
2018-02-14 10:28 ` [PATCH V2 net-next 7/7] selftests/net: add zerocopy support for PF_RDS test case Sowmini Varadhan
2018-02-15 0:19 ` [PATCH V2 net-next 0/7] RDS: zerocopy support Willem de Bruijn
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=4f85d732-f060-9510-6fdb-1458aa4cf435@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sowmini.varadhan@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).