linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Tom Talpey <tom@talpey.com>
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 19:37:34 -0300	[thread overview]
Message-ID: <20201016223734.GG36674@ziepe.ca> (raw)
In-Reply-To: <b7cc3571-5c4b-d5f1-d4e4-97afba4a7994@talpey.com>

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..

Jason

  reply	other threads:[~2020-10-16 22:37 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 [this message]
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=20201016223734.GG36674@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=lihao2018.fnst@cn.fujitsu.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tom@talpey.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).