[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cbbb7a4d-1c96-1102-45fc-5f0ffb329518@huawei.com>
Date: Sat, 29 Oct 2022 10:35:26 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: Peter Xu <peterx@...hat.com>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>
CC: Huang Ying <ying.huang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
HORIGUCHI NAOYA <naoya.horiguchi@....com>,
David Hildenbrand <david@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>
Subject: Re: [PATCH RFC 1/2] mm: Always compile in pte markers
On 2022/10/25 4:48, Peter Xu wrote:
> The PTE markers code is tiny and now it's enabled for most of the
> distributions. It's fine to keep it as-is, but to make a broader use of
> it (e.g. replacing read error swap entry) it needs to be there always
> otherwise we need special code path to take care of !PTE_MARKER case.
>
> It'll be easier just make pte marker always exist. Use this chance to
> extend its usage to anonymous too by simply touching up some of the old
> comments, because it'll be used for anonymous pages in the follow up
> patches.
>
> Signed-off-by: Peter Xu <peterx@...hat.com>
Many thanks for your work.
Reviewed-by: Miaohe Lin <linmiaohe@...wei.com>
Thanks,
Miaohe Lin
Powered by blists - more mailing lists