From: leon@kernel.org (Leon Romanovsky)
Subject: NVMe over Fabrics I/O Error with RDMA/RXE
Date: Mon, 9 Jul 2018 11:17:18 +0300 [thread overview]
Message-ID: <20180709081718.GA3014@mtr-leonro.mtl.com> (raw)
In-Reply-To: <4F63AE27-CBFD-4429-8BF9-ADEE946A9DB7@connect.ust.hk>
On Mon, Jul 09, 2018@04:06:05AM +0000, Bairen YI wrote:
> Hi all,
>
<...>
>
> Does NVMeof support over RXE or other software RDMA (like SoftiWarp) now?
NVMeof is card-agnostic, so it is supposed to work on RXE.
Thansk
>
> Best,
> Bairen Yi--
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180709/1d373a25/attachment.sig>
next prev parent reply other threads:[~2018-07-09 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 4:06 NVMe over Fabrics I/O Error with RDMA/RXE Bairen YI
2018-07-09 8:17 ` Leon Romanovsky [this message]
2018-07-09 10:42 ` Sagi Grimberg
2018-07-11 9:44 ` Bairen YI
2018-07-11 10:37 ` Sagi Grimberg
2018-07-12 5:54 ` Bairen YI
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=20180709081718.GA3014@mtr-leonro.mtl.com \
--to=leon@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