[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <806ba56d-3213-bd9a-b52e-b54be19885d7@suse.cz>
Date: Tue, 6 Nov 2018 13:06:24 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Aaron Lu <aaron.lu@...el.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Paweł Staszewski <pstaszewski@...are.pl>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Eric Dumazet <eric.dumazet@...il.com>,
Tariq Toukan <tariqt@...lanox.com>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Yoel Caspersen <yoel@...knet.dk>,
Mel Gorman <mgorman@...hsingularity.net>,
Saeed Mahameed <saeedm@...lanox.com>,
Michal Hocko <mhocko@...e.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>
Subject: Re: [PATCH v3 2/2] mm/page_alloc: use a single function to free page
On 11/6/18 12:31 PM, Aaron Lu wrote:
> We have multiple places of freeing a page, most of them doing similar
> things and a common function can be used to reduce code duplicate.
>
> It also avoids bug fixed in one function but left in another.
>
> Signed-off-by: Aaron Lu <aaron.lu@...el.com>
Acked-by: Vlastimil Babka <vbabka@...e.cz>
Thanks!
> ---
> v3: Vlastimil mentioned the possible performance loss by using
> page_ref_sub_and_test(page, 1) for put_page_testzero(page), since
> we aren't sure so be safe by keeping page ref decreasing code as
> is, only move freeing page part to a common function.
Powered by blists - more mailing lists