From: Christopher Lameter <cl@linux.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: John Hubbard <jhubbard@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, Michal Hocko <mhocko@kernel.org>
Subject: Re: [LSFMM] RDMA data corruption potential during FS writeback
Date: Mon, 21 May 2018 13:37:14 +0000 [thread overview]
Message-ID: <0100016382eb15e3-ce5d246f-1f88-401b-8a19-9a59f9707fe5-000000@email.amazonses.com> (raw)
In-Reply-To: <20180519032400.GA12517@ziepe.ca>
On Fri, 18 May 2018, Jason Gunthorpe wrote:
> Ummm, RDMA has done essentially that since 2005, since when did it
> become wrong? Do you have some references? Is there some alternative?
It was wrong from the start. It became much more evident with widespread
use of RDMA. The inability to scale processor performance at this point
but the huge increase in network bandwidth available forces users into
RDMA solution. Thus they will try to do RDMA to file backed mappings where
in the past we only used anonymous memory for RDMA.
next prev parent reply other threads:[~2018-05-21 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 14:37 Christopher Lameter
2018-05-18 15:49 ` Jason Gunthorpe
2018-05-18 16:47 ` Christopher Lameter
2018-05-18 17:36 ` Jason Gunthorpe
2018-05-18 20:23 ` Dan Williams
2018-05-19 2:33 ` John Hubbard
2018-05-19 3:24 ` Jason Gunthorpe
2018-05-19 3:51 ` Dan Williams
2018-05-19 5:38 ` John Hubbard
2018-05-21 14:38 ` Matthew Wilcox
2018-05-23 23:03 ` John Hubbard
2018-05-21 13:37 ` Christopher Lameter [this message]
2018-05-21 13:59 ` Christopher Lameter
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=0100016382eb15e3-ce5d246f-1f88-401b-8a19-9a59f9707fe5-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mhocko@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