[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0C8CC772-5840-4F0C-9859-C1D7B8BF6025@redhat.com>
Date: Fri, 28 Feb 2020 07:13:33 +0100
From: David Hildenbrand <david@...hat.com>
To: "Huang, Ying" <ying.huang@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
David Hildenbrand <david@...hat.com>,
Mel Gorman <mgorman@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Zi Yan <ziy@...dia.com>, Michal Hocko <mhocko@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Minchan Kim <minchan@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Hugh Dickins <hughd@...gle.com>
Subject: Re: [RFC 2/3] mm: Add a new page flag PageLayzyFree() for MADV_FREE
> Am 28.02.2020 um 04:38 schrieb Huang, Ying <ying.huang@...el.com>:
>
> From: Huang Ying <ying.huang@...el.com>
>
> Now !PageSwapBacked() is used as the flag for the pages freed lazily
> via MADV_FREE. This isn't obvious enough. So Dave suggested to add a
> new page flag for that to improve the code readability.
This patch subject and description is *really* confusing. You‘re adding a helper function, not a page flag. It‘s a fairly easy refactoring.
(Adding new page flags is close to impossible).
Cheers!
Powered by blists - more mailing lists