From: Jason Gunthorpe <jgg@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: "Wan, Kaike" <kaike.wan@intel.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"Rimmer, Todd" <todd.rimmer@intel.com>
Subject: Re: [PATCH RFC 0/9] A rendezvous module
Date: Fri, 19 Mar 2021 17:30:43 -0300 [thread overview]
Message-ID: <20210319203043.GD2356281@nvidia.com> (raw)
In-Reply-To: <ed0d861c-4352-8568-b3c0-31a0f1eac228@cornelisnetworks.com>
On Fri, Mar 19, 2021 at 04:18:56PM -0400, Dennis Dalessandro wrote:
> I was just providing some background/clarification. Bottom line this has
> nothing to do with hfi1 or OPA or PSM2.
Well, I hope your two companies can agree on naming if Cornelis
someday needs a PSM3 for it's HW.
Jason
next prev parent reply other threads:[~2021-03-19 20:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 12:56 [PATCH RFC 0/9] A rendezvous module kaike.wan
2021-03-19 12:56 ` [PATCH RFC 1/9] RDMA/rv: Public interferce for the RDMA Rendezvous module kaike.wan
2021-03-19 16:00 ` Jason Gunthorpe
2021-03-19 18:42 ` kernel test robot
2021-03-19 12:56 ` [PATCH RFC 2/9] RDMA/rv: Add the internal header files kaike.wan
2021-03-19 16:02 ` Jason Gunthorpe
2021-03-19 12:56 ` [PATCH RFC 3/9] RDMA/rv: Add the rv module kaike.wan
2021-03-19 12:56 ` [PATCH RFC 4/9] RDMA/rv: Add functions for memory region cache kaike.wan
2021-03-19 12:56 ` [PATCH RFC 5/9] RDMA/rv: Add function to register/deregister memory region kaike.wan
2021-03-19 12:56 ` [PATCH RFC 6/9] RDMA/rv: Add connection management functions kaike.wan
2021-03-19 12:56 ` [PATCH RFC 7/9] RDMA/rv: Add functions for RDMA transactions kaike.wan
2021-03-19 12:56 ` [PATCH RFC 8/9] RDMA/rv: Add functions for file operations kaike.wan
2021-03-19 12:56 ` [PATCH RFC 9/9] RDMA/rv: Integrate the file operations into the rv module kaike.wan
2021-03-19 13:53 ` [PATCH RFC 0/9] A rendezvous module Jason Gunthorpe
2021-03-19 14:49 ` Wan, Kaike
2021-03-19 15:48 ` Jason Gunthorpe
2021-03-19 19:22 ` Dennis Dalessandro
2021-03-19 19:44 ` Jason Gunthorpe
2021-03-19 20:12 ` Rimmer, Todd
2021-03-19 20:26 ` Jason Gunthorpe
2021-03-19 20:46 ` Rimmer, Todd
2021-03-19 20:54 ` Jason Gunthorpe
2021-03-19 20:59 ` Wan, Kaike
2021-03-19 21:28 ` Dennis Dalessandro
2021-03-19 21:58 ` Wan, Kaike
2021-03-19 22:35 ` Jason Gunthorpe
2021-03-19 22:57 ` Rimmer, Todd
2021-03-19 23:06 ` Jason Gunthorpe
2021-03-20 16:39 ` Dennis Dalessandro
2021-03-21 8:56 ` Leon Romanovsky
2021-03-21 16:24 ` Dennis Dalessandro
2021-03-21 16:45 ` Jason Gunthorpe
2021-03-21 17:21 ` Dennis Dalessandro
2021-03-21 18:08 ` Jason Gunthorpe
2021-03-22 15:17 ` Rimmer, Todd
2021-03-22 16:47 ` Jason Gunthorpe
2021-03-22 17:31 ` Hefty, Sean
2021-03-23 22:56 ` Jason Gunthorpe
2021-03-23 23:29 ` Rimmer, Todd
2021-03-21 19:19 ` Wan, Kaike
2021-03-23 15:36 ` Christoph Hellwig
2021-03-23 15:35 ` Christoph Hellwig
2021-03-23 15:33 ` Christoph Hellwig
2021-03-23 15:30 ` Christoph Hellwig
2021-03-23 15:46 ` Jason Gunthorpe
2021-03-23 16:07 ` Christoph Hellwig
2021-03-23 17:25 ` Rimmer, Todd
2021-03-23 17:44 ` Jason Gunthorpe
2021-03-19 20:18 ` Dennis Dalessandro
2021-03-19 20:30 ` Jason Gunthorpe [this message]
2021-03-19 20:34 ` Hefty, Sean
2021-03-21 12:08 ` Jason Gunthorpe
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=20210319203043.GD2356281@nvidia.com \
--to=jgg@nvidia.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=kaike.wan@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=todd.rimmer@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.