From: Jason Gunthorpe <jgg@mellanox.com>
To: Jerome Glisse <jglisse@redhat.com>
Cc: Ralph Campbell <rcampbell@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Christoph Hellwig <hch@lst.de>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v2 2/3] mm/hmm: allow snapshot of the special zero page
Date: Tue, 22 Oct 2019 17:41:11 +0000 [thread overview]
Message-ID: <20191022174107.GM22766@mellanox.com> (raw)
In-Reply-To: <20191022173026.GB5169@redhat.com>
On Tue, Oct 22, 2019 at 01:30:26PM -0400, Jerome Glisse wrote:
> > Smart drivers can test somehow for pfn == zero_page and optimize?
>
> There is nothing to optimize here, i do not know any hardware that
> have a special page table entry that make all memory access return
> zero.
Presumably any GPU could globally dedicate one page of internal memory
as a zero page and remap CPU zero page to that internal memory page?
This is basically how the CPU zero page works.
I suspect mlx5 could do the same with its internal memory, but the
internal memory is too limited to make this worth while.
mlx5 also has a specially 'zero MR' that always reads as zero (and
discards writes), but it doesn't quite fit well into the ODP flow.
Jason
next prev parent reply other threads:[~2019-10-22 17:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 20:48 [PATCH v2 0/3] HMM tests and minor fixes Ralph Campbell
2019-10-15 20:48 ` [PATCH v2 1/3] mm/hmm: make full use of walk_page_range() Ralph Campbell
2019-10-21 18:32 ` Jason Gunthorpe
2019-10-21 20:32 ` Ralph Campbell
2019-10-15 20:48 ` [PATCH v2 2/3] mm/hmm: allow snapshot of the special zero page Ralph Campbell
2019-10-21 18:08 ` Jason Gunthorpe
2019-10-21 20:08 ` Ralph Campbell
2019-10-21 18:49 ` Jerome Glisse
2019-10-21 20:54 ` Ralph Campbell
2019-10-22 2:45 ` Jerome Glisse
2019-10-22 15:05 ` Jason Gunthorpe
2019-10-22 17:06 ` Jerome Glisse
2019-10-22 17:09 ` Jason Gunthorpe
2019-10-22 17:30 ` Jerome Glisse
2019-10-22 17:41 ` Jason Gunthorpe [this message]
2019-10-22 17:52 ` Jerome Glisse
2019-10-15 20:48 ` [PATCH v2 3/3] mm/hmm/test: add self tests for HMM Ralph Campbell
2019-10-21 18:50 ` Jerome Glisse
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=20191022174107.GM22766@mellanox.com \
--to=jgg@mellanox.com \
--cc=hch@lst.de \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rcampbell@nvidia.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