[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1404111057390.13278@nuc>
Date: Fri, 11 Apr 2014 10:57:54 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Vladimir Davydov <vdavydov@...allels.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 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
--
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