From: Tom Talpey <tom@talpey.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Li, Hao" <lihao2018.fnst@cn.fujitsu.com>, linux-rdma@vger.kernel.org
Subject: Re: Question about supporting RDMA Extensions for PMEM
Date: Fri, 16 Oct 2020 20:22:21 -0400 [thread overview]
Message-ID: <fa3e23a4-49fe-efa2-04dd-1264b352d8cb@talpey.com> (raw)
In-Reply-To: <20201016223734.GG36674@ziepe.ca>
On 10/16/2020 6:37 PM, Jason Gunthorpe wrote:
> On Mon, Oct 12, 2020 at 10:26:32PM -0400, Tom Talpey wrote:
>
>> In theory, the IBTA SWG is in control of specifying any Verbs changes.
>
> SWG and IETF should agree on what the general software presentation
> should look like so HW implementations can be compatible.
>
> It looks fairly straightforward so this probably isn't strictly
> necessary once the one the wire protocol is decided.
>
> verbs has a life of its own these days outside IBTA/IETF..
For the record, I completely agree with the goal of compatible
interfaces. And, I'm committed to defining it, however I am not
able to participate in IBTA as I am no longer associated with
any IBTA member company. I am active in IETF, which has no such
restriction.
However, it's also important to point out that IETF considers
programming interfaces to be out of scope. The draft-hilland-verbs
document for iWARP was not adopted as a work item, and its
content, while extraordinary useful, is not an IETF product.
As an example, consider TCP and Sockets. IETF owns the former,
and has no input on the latter.
In other words, I think it's on us.
Tom.
prev parent reply other threads:[~2020-10-17 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 8:13 Question about supporting RDMA Extensions for PMEM Li, Hao
2020-10-13 2:26 ` Tom Talpey
2020-10-16 22:37 ` Jason Gunthorpe
2020-10-17 0:22 ` Tom Talpey [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=fa3e23a4-49fe-efa2-04dd-1264b352d8cb@talpey.com \
--to=tom@talpey.com \
--cc=jgg@ziepe.ca \
--cc=lihao2018.fnst@cn.fujitsu.com \
--cc=linux-rdma@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 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).