From: Haggai Eran <haggaie@mellanox.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Matthew Wilcox <willy@linux.intel.com>
Cc: Stephen Bates <stephen.bates@pmcs.com>,
linux-mm@kvack.org, linux-rdma@vger.kernel.org,
linux-nvdimm@ml01.01.org, javier@cnexlabs.com,
sagig@mellanox.com, leonro@mellanox.com, artemyko@mellanox.com,
hch@infradead.org
Subject: Re: [PATCH RFC 1/1] Add support for ZONE_DEVICE IO memory with struct pages.
Date: Thu, 17 Mar 2016 17:18:11 +0200 [thread overview]
Message-ID: <56EACAB3.5070301@mellanox.com> (raw)
In-Reply-To: <20160314215708.GA7282@obsidianresearch.com>
On 3/14/2016 11:57 PM, Jason Gunthorpe wrote:
> The other issue is that the fencing mechanism RDMA uses to create
> ordering with system memory is not good enough to fence peer-peer
> transactions in the general case. It is only possibly good enough if
> all the transactions run through the root complex.
Are you sure this is a problem? I'm not sure it is clear in the PCIe
specs, but I thought that for transactions that are not relaxed-ordered
and don't use ID-based ordering, a PCIe switch must prevent reads and
writes from passing writes. I assume this is true even when the requestor
ID is different because IDO relaxes these constraints specifically
for transactions coming from different requestor IDs.
Regards,
Haggai
--
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>
next prev parent reply other threads:[~2016-03-17 15:23 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 [this message]
2016-03-17 16:11 ` Jason Gunthorpe
2016-03-21 19:25 ` Stephen Bates
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=56EACAB3.5070301@mellanox.com \
--to=haggaie@mellanox.com \
--cc=artemyko@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=stephen.bates@pmcs.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