[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f56a750a54eadf76c45d3065622d4cbf@codeaurora.org>
Date: Thu, 27 Sep 2018 13:39:41 +0530
From: Arun KS <arunks@...eaurora.org>
To: Oscar Salvador <osalvador@...hadventures.net>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
boris.ostrovsky@...cle.com, jgross@...e.com,
akpm@...ux-foundation.org, dan.j.williams@...el.com,
mhocko@...e.com, vbabka@...e.cz, iamjoonsoo.kim@....com,
gregkh@...uxfoundation.org, osalvador@...e.de, malat@...ian.org,
kirill.shutemov@...ux.intel.com, jrdr.linux@...il.com,
yasu.isimatu@...il.com, mgorman@...hsingularity.net,
aaron.lu@...el.com, devel@...uxdriverproject.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
xen-devel@...ts.xenproject.org, vatsa@...eaurora.org,
vinmenon@...eaurora.org, getarunks@...il.com
Subject: Re: [PATCH v3] memory_hotplug: Free pages as higher order
On 2018-09-27 12:39, Oscar Salvador wrote:
> On Thu, Sep 27, 2018 at 12:28:50PM +0530, Arun KS wrote:
>> + __free_pages_boot_core(page, order);
>
Hi,
> I am not sure, but if we are going to use that function from the
> memory-hotplug code,
> we might want to rename that function to something more generic?
> The word "boot" suggests that this is only called from the boot stage.
I ll rename it to __free_pages_core()
>
> And what about the prefetch operations?
> I saw that you removed them in your previous patch and that had some
> benefits [1].
>
> Should we remove them here as well?
Sure. Will update this as well.
Thanks,
Arun
>
> [1] https://patchwork.kernel.org/patch/10613359/
>
> Thanks
Powered by blists - more mailing lists