[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b56e156b911e943eba3a1daa0a1cb31@codeaurora.org>
Date: Tue, 09 Oct 2018 15:24:13 +0530
From: Arun KS <arunks@...eaurora.org>
To: Michal Hocko <mhocko@...nel.org>
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,
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 v5 1/2] memory_hotplug: Free pages as higher order
On 2018-10-09 14:59, Michal Hocko wrote:
> On Fri 05-10-18 13:40:05, Arun KS wrote:
>> When free pages are done with higher order, time spend on
>> coalescing pages by buddy allocator can be reduced. With
>> section size of 256MB, hot add latency of a single section
>> shows improvement from 50-60 ms to less than 1 ms, hence
>> improving the hot add latency by 60%. Modify external
>> providers of online callback to align with the change.
>
> Acked-by: Michal Hocko <mhocko@...e.com>
>
> Thanks for your patience with all the resubmission.
Hello Michal,
I got the below email few days back. Do I still need to resubmit the
patch? or is it already on the way to merge?
Regards,
Arun
The patch titled
Subject: mm/page_alloc.c: memory hotplug: free pages as higher
order
has been added to the -mm tree. Its filename is
memory_hotplug-free-pages-as-higher-order.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/memory_hotplug-free-pages-as-higher-order.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/memory_hotplug-free-pages-as-higher-order.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when
testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
Powered by blists - more mailing lists