[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130923171108.GG14547@htj.dyndns.org>
Date: Mon, 23 Sep 2013 13:11:08 -0400
From: Tejun Heo <tj@...nel.org>
To: Zhang Yanfei <zhangyanfei.yes@...il.com>
Cc: Tang Chen <tangchen@...fujitsu.com>, rjw@...k.pl, lenb@...nel.org,
tglx@...utronix.de, mingo@...e.hu, hpa@...or.com,
akpm@...ux-foundation.org, toshi.kani@...com,
zhangyanfei@...fujitsu.com, liwanp@...ux.vnet.ibm.com,
trenn@...e.de, yinghai@...nel.org, jiang.liu@...wei.com,
wency@...fujitsu.com, laijs@...fujitsu.com,
isimatu.yasuaki@...fujitsu.com, izumi.taku@...fujitsu.com,
mgorman@...e.de, minchan@...nel.org, mina86@...a86.com,
gong.chen@...ux.intel.com, vasilis.liaskovitis@...fitbricks.com,
lwoodman@...hat.com, riel@...hat.com, jweiner@...hat.com,
prarit@...hat.com, x86@...nel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-acpi@...r.kernel.org
Subject: Re: [PATCH v3 5/5] mem-hotplug: Introduce movablenode boot option to
control memblock allocation direction.
Hello,
On Tue, Sep 24, 2013 at 12:58:03AM +0800, Zhang Yanfei wrote:
> you mean we define memblock_set_bottom_up and memblock_bottom_up like below:
>
> #ifdef CONFIG_MOVABLE_NODE
> void memblock_set_bottom_up(bool enable)
> {
> /* do something */
> }
>
> bool memblock_bottom_up()
> {
> return direction == bottom_up;
> }
> #else
> void memblock_set_bottom_up(bool enable)
> {
> /* empty */
> }
>
> bool memblock_bottom_up()
> {
> return false;
> }
> #endif
>
> right?
Yeah, the compiler would be able to drop bottom_up code if
!MOVABLE_NODE as long as the implementation functions are static.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists