linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Max Gurtovoy <maxg@mellanox.com>
To: Christoph Hellwig <hch@infradead.org>,
	Talker Alex <alextalker@yandex.ru>
Cc: linux-nvme@lists.infradead.org
Subject: Re: NVMe/IB support
Date: Thu, 20 Feb 2020 16:13:07 +0200	[thread overview]
Message-ID: <e2f116a2-ee5a-ee53-32c2-1f1e8d998567@mellanox.com> (raw)
In-Reply-To: <20200219152053.GA13942@infradead.org>


On 2/19/2020 5:20 PM, Christoph Hellwig wrote:
> On Fri, Feb 07, 2020 at 03:43:22PM +0300, Talker Alex wrote:
>> Hi,
>>
>> is there really exist NVMe/IB solutions?
> All the original NVMeoF development was done on IB, just using the
> RDMA/CM IP based addressing.

I guess we can consider adding this code one day, for users that can't 
use RDMA/CM (SRP supports both options).

>
> _______________________________________________
> linux-nvme mailing list
> linux-nvme@lists.infradead.org
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infradead.org%2Fmailman%2Flistinfo%2Flinux-nvme&amp;data=02%7C01%7Cmaxg%40mellanox.com%7C6a85529d21224f373a3708d7b54f5253%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C637177224606112903&amp;sdata=QpJWMIFVoKqlWZLdlNcbvEnRS2RlLGmTzIiVNoB4ueA%3D&amp;reserved=0

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-02-20 14:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 12:43 NVMe/IB support Talker Alex
2020-02-08  1:39 ` Sagi Grimberg
2020-02-19 15:20 ` Christoph Hellwig
2020-02-20 14:13   ` Max Gurtovoy [this message]
2020-02-20 14:25     ` Christoph Hellwig
2020-02-20 15:16       ` Max Gurtovoy
2020-02-20 15:33         ` Christoph Hellwig
2020-02-20 16:29           ` Sagi Grimberg

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=e2f116a2-ee5a-ee53-32c2-1f1e8d998567@mellanox.com \
    --to=maxg@mellanox.com \
    --cc=alextalker@yandex.ru \
    --cc=hch@infradead.org \
    --cc=linux-nvme@lists.infradead.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).