[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090914175942.GH11778@csn.ul.ie>
Date: Mon, 14 Sep 2009 18:59:42 +0100
From: Mel Gorman <mel@....ul.ie>
To: Christoph Lameter <cl@...ux-foundation.org>
Cc: Zhu Yi <yi.zhu@...el.com>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
Frans Pop <elendil@...net.nl>,
Larry Finger <Larry.Finger@...inger.net>,
"John W. Linville" <linville@...driver.com>,
Pekka Enberg <penberg@...helsinki.fi>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"ipw3945-devel@...ts.sourceforge.net"
<ipw3945-devel@...ts.sourceforge.net>,
Andrew Morton <akpm@...ux-foundation.org>,
"Krauss, Assaf" <assaf.krauss@...el.com>,
Johannes Berg <johannes@...solutions.net>,
"Abbas, Mohamed" <mohamed.abbas@...el.com>
Subject: Re: iwlagn: order 2 page allocation failures
On Mon, Sep 14, 2009 at 11:42:15AM -0400, Christoph Lameter wrote:
> On Mon, 14 Sep 2009, Zhu Yi wrote:
>
> > BTW, does SLAB/SLUB guarantee size of multiple PAGE_SIZE __kmalloc()
> > allocation align on PAGE_SIZE (or 256 bytes) boundary?
>
> Page allocators guarantee page aligned data. Slab allocators do not.
>
> You can create a slab that aligns objects on 256 byte boundary if you
> want.
>
The allocation of buffers >= PAGE_SIZE even when allocated with
kmalloc() are page-aligned though right? It's not an explicit guarantee
but is it not always the case?
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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