From: Christoph Hellwig <hch@infradead.org>
To: Dan Greenfield <dgrnfld@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: XFS NVMe RDMA?
Date: Thu, 11 Nov 2021 22:40:08 -0800 [thread overview]
Message-ID: <YY4MSDOJKc64JcU/@infradead.org> (raw)
In-Reply-To: <3CBB4EC9-5953-4276-8219-DA8B10ABB05F@gmail.com>
Hi Dan,
sorry for the late reply. This sat in my outbox for a while almost
fully written.
On Wed, Oct 27, 2021 at 09:23:42AM +0100, Dan Greenfield wrote:
> Quick Question: would I be correct in assuming that if I mmap()ed each 8-64MB (chunk) file from XFS, and then did RDMA from the mmap region, that it would first be copied from NVMe into DRAM (does this bypass CPU?) and *then* be copied across RDMA, rather than directly be copied from NVMe by RDMA? Or does O_DIRECT properly allow bypass straight to NVMe for RDMA?
The answer is: it depends. mmap on a non-DAX file system always copied
into DRAM. mmap on a DAX file system (that is using pmem) can map
the "storage" directly into memory, in which case some RDMA setups can
DMA without a copy.
But with a plain old SSD there is no path available to userspace to
transfer without copying to DRAM. If OTOH you use in-kernel NVMe over
fabics target, it can directly transfers from the SSDs in some
circumstances. Currently that does require using the SSD directly
without a file system, but with a little more work it could also work
using a file system.
prev parent reply other threads:[~2021-11-12 6:40 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
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 [this message]
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=YY4MSDOJKc64JcU/@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