[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ce89fe94-dc8d-4e10-9181-e01760939ef6@lucifer.local>
Date: Mon, 20 Mar 2023 08:40:40 +0000
From: Lorenzo Stoakes <lstoakes@...il.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Baoquan He <bhe@...hat.com>,
Uladzislau Rezki <urezki@...il.com>,
David Hildenbrand <david@...hat.com>,
Liu Shixin <liushixin2@...wei.com>,
Jiri Olsa <jolsa@...nel.org>
Subject: Re: [PATCH v2 2/4] mm: vmalloc: use rwsem, mutex for vmap_area_lock
and vmap_block->lock
On Sun, Mar 19, 2023 at 09:16:18PM +0000, Lorenzo Stoakes wrote:
> On Sun, Mar 19, 2023 at 08:47:14PM +0000, Matthew Wilcox wrote:
> > I wonder if we can't do something like prefaulting the page before
> > taking the spinlock, then use copy_page_to_iter_atomic()
>
<snip>
On second thoughts, and discussing with Uladzislau, this seems like a more
sensible approach.
I'm going to respin with prefaulting and revert to the previous locking.
Powered by blists - more mailing lists