[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52328839.9010309@cn.fujitsu.com>
Date: Fri, 13 Sep 2013 11:36:25 +0800
From: Tang Chen <tangchen@...fujitsu.com>
To: Toshi Kani <toshi.kani@...com>
CC: tj@...nel.org, rjw@...k.pl, lenb@...nel.org, tglx@...utronix.de,
mingo@...e.hu, hpa@...or.com, akpm@...ux-foundation.org,
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, zhangyanfei@...fujitsu.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: [RESEND PATCH v2 3/9] x86, dma: Support allocate memory from
bottom upwards in dma_contiguous_reserve().
Hi Toshi,
On 09/13/2013 03:22 AM, Toshi Kani wrote:
......
>> + if (memblock_direction_bottom_up()) {
>> + addr = memblock_alloc_bottom_up(
>> + MEMBLOCK_ALLOC_ACCESSIBLE,
>> + limit, size, alignment);
>> + if (addr)
>> + goto success;
>> + }
>
> I am afraid that this version went to a wrong direction. Allocating
> from the bottom up needs to be an internal logic within the memblock
> allocator. It should not require the callers to be aware of the
> direction and make a special request.
>
I think my v1 patch-set was trying to do so. Was it too complicated ?
So just move this logic to memblock_find_in_range_node(), is this OK ?
Thanks.
--
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