[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZAi8+PCsIzExWPQN@x1n>
Date: Wed, 8 Mar 2023 11:51:04 -0500
From: Peter Xu <peterx@...hat.com>
To: David Hildenbrand <david@...hat.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Muhammad Usama Anjum <usama.anjum@...labora.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Axel Rasmussen <axelrasmussen@...gle.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Nadav Amit <nadav.amit@...il.com>,
Paul Gofman <pgofman@...eweavers.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v3 1/2] mm/uffd: UFFD_FEATURE_WP_UNPOPULATED
On Wed, Mar 08, 2023 at 04:57:55PM +0100, David Hildenbrand wrote:
> Oh, my thinking was that with markers you postpone placing the shared
> zeropage. So the next read access will require a pagefault to map the shared
> zeropage. Your v1 would have performed best in that case I guess.
Ah, so I misunderstood because the sentence being quote was in another
context I think..
Pagemap may bring overhead constantly though, not sure when vs page faults.
May relevant to num of missing pages.
It's just that we may still want pte markers to avoid losing MISSING+WP
(with WP_UNPOPULATED) use case, which you rightfully pointed out before.
--
Peter Xu
Powered by blists - more mailing lists