From: Tom Talpey <tom@talpey.com>
To: "Li, Hao" <lihao2018.fnst@cn.fujitsu.com>, linux-rdma@vger.kernel.org
Subject: Re: Question about supporting RDMA Extensions for PMEM
Date: Mon, 12 Oct 2020 22:26:32 -0400 [thread overview]
Message-ID: <b7cc3571-5c4b-d5f1-d4e4-97afba4a7994@talpey.com> (raw)
In-Reply-To: <8b3c3c81-c0fd-adb2-52a9-94c73aac7e37@cn.fujitsu.com>
On 10/12/2020 4:13 AM, Li, Hao wrote:
> Hi,
>
> I have noticed that IETF has released a draft of RDMA Extensions for
> PMEM [1]. Does libibverbs has a plan to implement these extensions? Are
> there some good starting points if we want to participate the development.
> Thanks!
>
> [1]: https://tools.ietf.org/id/draft-talpey-rdma-commit-01.html
The draft you refer to is an individual draft, not an official IETF
release. However, after a lengthy process, the effort is now an official
work item of the NFSv4 working group, since the original STORM WG was
shut down an alternative process had to be determined.
An updated document is in the works, hopefully in October, and may
become a full RFC as the IETF process advances. My coauthors and I look
forward to this.
In the meantime, the IBTA LWG took up a similar task, and we completed
it several months ago. I am not sure when it might be released as an
official Annex, but I assume that is in the works as well. The IBTA
version of the extensions is semantically similar, but does not include
the "Verify" operation which in the iWARP document. Perhaps this will
be added later.
In theory, the IBTA SWG is in control of specifying any Verbs changes.
The Annex does discuss these, but SWG would still need to ratify. If
Fujitsu is an IBTA member, I'd encourage you to support this. IETF, of
course, has no dependency on IBTA, or Verbs, so participating there is
a separate matter. I encourage that participation, too!
Tom.
next prev parent reply other threads:[~2020-10-13 2:42 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 [this message]
2020-10-16 22:37 ` Jason Gunthorpe
2020-10-17 0:22 ` Tom Talpey
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=b7cc3571-5c4b-d5f1-d4e4-97afba4a7994@talpey.com \
--to=tom@talpey.com \
--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