From: Arun KS <arunks@codeaurora.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, boris.ostrovsky@oracle.com,
jgross@suse.com, akpm@linux-foundation.org,
dan.j.williams@intel.com, iamjoonsoo.kim@lge.com,
osalvador@suse.de, malat@debian.org, yasu.isimatu@gmail.com,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, xen-devel@lists.xenproject.org,
vatsa@codeaurora.org, vinmenon@codeaurora.org,
getarunks@gmail.com
Subject: Re: [PATCH v2] memory_hotplug: Free pages as higher order
Date: Wed, 26 Sep 2018 16:27:08 +0530 [thread overview]
Message-ID: <bdba4200b69f560af36967e2d23dde8f@codeaurora.org> (raw)
In-Reply-To: <20180925181826.GW18685@dhcp22.suse.cz>
On 2018-09-25 23:48, Michal Hocko wrote:
> On Tue 25-09-18 11:59:09, Vlastimil Babka wrote:
> [...]
>> This seems like almost complete copy of __free_pages_boot_core(),
>> could
>> you do some code reuse instead? I think Michal Hocko also suggested
>> that.
>
> Yes, please try to reuse as much code as possible
Sure, Will address in next spin.
Regards,
Arun
next prev parent reply other threads:[~2018-09-26 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 5:42 [PATCH v2] memory_hotplug: Free pages as higher order Arun KS
2018-09-25 9:59 ` Vlastimil Babka
2018-09-25 9:59 ` Vlastimil Babka
2018-09-25 18:18 ` Michal Hocko
2018-09-25 18:18 ` Michal Hocko
2018-09-26 10:57 ` Arun KS
2018-09-26 10:57 ` Arun KS [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-25 5:42 Arun KS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bdba4200b69f560af36967e2d23dde8f@codeaurora.org \
--to=arunks@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=devel@linuxdriverproject.org \
--cc=getarunks@gmail.com \
--cc=haiyangz@microsoft.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jgross@suse.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=sthemmin@microsoft.com \
--cc=vatsa@codeaurora.org \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yasu.isimatu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.