From: Christoph Hellwig <hch@infradead.org>
To: Dan Greenfield <dgrnfld@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS NVMe RDMA?
Date: Wed, 20 Oct 2021 09:33:43 -0700 [thread overview]
Message-ID: <YXBE5y2cJtAaMfzs@infradead.org> (raw)
In-Reply-To: <965EC18A-BF96-4544-AFE0-FA0F1787FD49@gmail.com>
On Wed, Oct 20, 2021 at 12:51:05PM +0100, Dan Greenfield wrote:
> Do you have any ideas how they could have been able to utilise RDMA so that node A can directly access data chunks stored on XFS on node B? Is the only approach to mmap the chunk on node B and then RDMA it to/from node A?
I'm not going to watch a video, but with the pNFS code other nodes can
access data on an XFS node directly using any SCSI transport.
For RMDA that would be SRP or iSCSI/iSER.
Note that I also have an unfinished draft to support NVMe, which has
an RDMA transports as well and someone else could trivially reimplement
that as well.
next prev parent reply other threads:[~2021-10-20 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 11:51 XFS NVMe RDMA? Dan Greenfield
2021-10-20 16:33 ` Christoph Hellwig [this message]
2021-10-20 16:35 ` Christoph Hellwig
2021-10-21 9:58 ` Dan Greenfield
2021-10-27 8:23 ` Dan Greenfield
2021-11-12 6:40 ` Christoph Hellwig
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=YXBE5y2cJtAaMfzs@infradead.org \
--to=hch@infradead.org \
--cc=dgrnfld@gmail.com \
--cc=linux-xfs@vger.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