From: Haggai Eran <haggaie@mellanox.com>
To: Stephen Bates <Stephen.Bates@pmcs.com>,
Sagi Grimberg <sagig@dev.mellanox.co.il>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Christoph Hellwig <hch@infradead.org>,
"'Logan Gunthorpe' (logang@deltatee.com)" <logang@deltatee.com>
Cc: Artemy Kovalyov <artemyko@mellanox.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Leon Romanovsky <leonro@mellanox.com>,
"sagig@mellanox.com" <sagig@mellanox.com>
Subject: Re: [RFC 0/7] Peer-direct memory
Date: Thu, 25 Feb 2016 13:27:45 +0200 [thread overview]
Message-ID: <56CEE531.5050807@mellanox.com> (raw)
In-Reply-To: <36F6EBABA23FEF4391AF72944D228901EB712F72@BBYEXM01.pmc-sierra.internal>
On 25/02/2016 01:45, Stephen Bates wrote:
> Great, we hope to have the RFC soon. It will be able to accept different flags for devm_memremap() call with regards to caching. Though one question I have is when does the caching flag affect Peer-2-Peer memory accesses? I can see caching causing issues when performing accesses from the CPU but P2P accesses should bypass any caches in the system?
I don't think the caching flag will affect peer to peer directly, but we need
to keep the BAR mapped to the host the same way it is today. If we change the
driver to map page structs returned from devm_memremap_pages() instead of using
io_remap_pfn_range() it needs to continue working with host uses and not only
with peers.
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>
prev parent reply other threads:[~2016-02-25 11:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455207177-11949-1-git-send-email-artemyko@mellanox.com>
[not found] ` <20160211191838.GA23675@obsidianresearch.com>
2016-02-14 14:27 ` Haggai Eran
2016-02-16 18:22 ` Jason Gunthorpe
2016-02-17 4:03 ` davide rossetti
2016-02-17 4:13 ` davide rossetti
2016-02-17 4:44 ` Jason Gunthorpe
2016-02-17 8:49 ` Christoph Hellwig
2016-02-18 17:12 ` Jason Gunthorpe
2016-02-17 8:44 ` Christoph Hellwig
2016-02-17 15:25 ` Haggai Eran
2016-02-19 18:54 ` Dan Williams
[not found] ` <20160212201328.GA14122@infradead.org>
[not found] ` <20160212203649.GA10540@obsidianresearch.com>
[not found] ` <56C09C7E.4060808@dev.mellanox.co.il>
[not found] ` <36F6EBABA23FEF4391AF72944D228901EB70C102@BBYEXM01.pmc-sierra.internal>
2016-02-21 9:06 ` Haggai Eran
2016-02-24 23:45 ` Stephen Bates
2016-02-25 11:27 ` Haggai Eran [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=56CEE531.5050807@mellanox.com \
--to=haggaie@mellanox.com \
--cc=Stephen.Bates@pmcs.com \
--cc=artemyko@mellanox.com \
--cc=dledford@redhat.com \
--cc=hch@infradead.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=leonro@mellanox.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=sagig@dev.mellanox.co.il \
--cc=sagig@mellanox.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