From: Stephen Bates <Stephen.Bates@pmcs.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Haggai Eran <haggaie@mellanox.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"javier@cnexlabs.com" <javier@cnexlabs.com>,
"sagig@mellanox.com" <sagig@mellanox.com>,
"leonro@mellanox.com" <leonro@mellanox.com>,
"artemyko@mellanox.com" <artemyko@mellanox.com>,
"hch@infradead.org" <hch@infradead.org>
Subject: RE: [PATCH RFC 1/1] Add support for ZONE_DEVICE IO memory with struct pages.
Date: Mon, 21 Mar 2016 19:25:29 +0000 [thread overview]
Message-ID: <36F6EBABA23FEF4391AF72944D228901EB72CA35@BBYEXM01.pmc-sierra.internal> (raw)
In-Reply-To: <20160317161121.GA19501@obsidianresearch.com>
>
> There are fringe cases that are more complex, and maybe the correct reading
> of the spec is to setup routing to avoid optimal paths, but it certainly is
> possible to configure switches in a way that could not guarentee global
> ordering.
>
> Jason
If someone configures a multipath PCIe topology I think they will have potential for out of order RDMA reads/writes regardless of whether the target MR is in system memory of PCIe memory. So I don't think these crazy topologies are uniquely problematic for IOPMEM.
Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-03-21 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 18:14 Stephen Bates
2016-03-14 21:23 ` Matthew Wilcox
2016-03-14 21:57 ` Jason Gunthorpe
2016-03-15 4:09 ` Logan Gunthorpe
2016-03-15 17:00 ` Stephen Bates
2016-03-17 15:18 ` Haggai Eran
2016-03-17 16:11 ` Jason Gunthorpe
2016-03-21 19:25 ` Stephen Bates [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=36F6EBABA23FEF4391AF72944D228901EB72CA35@BBYEXM01.pmc-sierra.internal \
--to=stephen.bates@pmcs.com \
--cc=artemyko@mellanox.com \
--cc=haggaie@mellanox.com \
--cc=hch@infradead.org \
--cc=javier@cnexlabs.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=leonro@mellanox.com \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagig@mellanox.com \
--cc=willy@linux.intel.com \
/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