From: Max Gurtovoy <maxg@mellanox.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Talker Alex <alextalker@yandex.ru>, linux-nvme@lists.infradead.org
Subject: Re: NVMe/IB support
Date: Thu, 20 Feb 2020 17:16:35 +0200 [thread overview]
Message-ID: <cd2f6306-1c4e-848c-9075-f89ce5f3a9ac@mellanox.com> (raw)
In-Reply-To: <20200220142517.GA20993@infradead.org>
On 2/20/2020 4:25 PM, Christoph Hellwig wrote:
> On Thu, Feb 20, 2020 at 04:13:07PM +0200, Max Gurtovoy wrote:
>> 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).
> The NVMeOF RDMA transport requires RDMA/CM. But RDMA/CM can also use
> IB addressing, which should be easy enough to implement if someone
> cares.
Are you saying that if one would like to use ADRFAM == AF_IB, he must
have RDMA/CM stack that support IB addressing ?
seems little bit weird requirement...
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-02-20 15:35 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
2020-02-20 14:25 ` Christoph Hellwig
2020-02-20 15:16 ` Max Gurtovoy [this message]
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=cd2f6306-1c4e-848c-9075-f89ce5f3a9ac@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).