[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53482555.4070603@parallels.com>
Date: Fri, 11 Apr 2014 21:24:37 +0400
From: Vladimir Davydov <vdavydov@...allels.com>
To: Christoph Lameter <cl@...ux.com>
CC: <akpm@...ux-foundation.org>, <penberg@...nel.org>,
<gthelen@...gle.com>, <hannes@...xchg.org>, <mhocko@...e.cz>,
<glommer@...il.com>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, <devel@...nvz.org>
Subject: Re: [PATCH -mm] slab: document kmalloc_order
On 04/11/2014 07:57 PM, Christoph Lameter wrote:
> On Fri, 11 Apr 2014, Vladimir Davydov wrote:
>
>> diff --git a/mm/slab_common.c b/mm/slab_common.c
>> index cab4c49b3e8c..3ffd2e76b5d2 100644
>> --- a/mm/slab_common.c
>> +++ b/mm/slab_common.c
>> @@ -573,6 +573,11 @@ void __init create_kmalloc_caches(unsigned long flags)
>> }
>> #endif /* !CONFIG_SLOB */
>>
>> +/*
>> + * To avoid unnecessary overhead, we pass through large allocation requests
>> + * directly to the page allocator. We use __GFP_COMP, because we will need to
>> + * know the allocation order to free the pages properly in kfree.
>> + */
>> void *kmalloc_order(size_t size, gfp_t flags, unsigned int order)
>> {
>> void *ret;
>>
> ??? kmalloc_order is defined in include/linux/slab.h
I moved it to slab_common.c in "[PATCH -mm v2.2] mm: get rid of
__GFP_KMEMCG"
--
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