[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01ca01cbee7b$4f790370$ee6b0a50$@mprc.pku.edu.cn>
Date: Wed, 30 Mar 2011 09:39:26 +0800
From: "Guan Xuetao" <gxt@...c.pku.edu.cn>
To: "'Arnd Bergmann'" <arnd@...db.de>
Cc: "'Paul Mundt'" <lethal@...ux-sh.org>,
<linux-kernel@...r.kernel.org>, <linux-fbdev@...r.kernel.org>
Subject: RE: [PATCH] unicore32 framebuffer driver fix: make videomemory kmalloc-ed and floatable
> -----Original Message-----
> From: Arnd Bergmann [mailto:arnd@...db.de]
> Sent: Tuesday, March 29, 2011 10:43 PM
> To: Guan Xuetao
> Cc: Paul Mundt; linux-kernel@...r.kernel.org; linux-fbdev@...r.kernel.org
> Subject: Re: [PATCH] unicore32 framebuffer driver fix: make videomemory kmalloc-ed and floatable
>
> On Tuesday 29 March 2011, Guan Xuetao wrote:
> >
> > 1. make videomemory kmalloc-ed in fb-puv3.c
> > 2. remove resource reservation for old fixed UNIGFX_MMAP & UVC_MMAP space
> > 3. remove unused PKUNTIY_UNIGFX_MMAP_BASE, PKUNITY_UNIGFX_MMAP_SIZE,
> > PKUNITY_UVC_MMAP_BASE, PKUNITY_UVC_MMAP_SIZE and KUSER_UNIGFX_BASE
> > 4. remove unused header linux/vmalloc.h in fb-puv3.c
> >
> > Signed-off-by: Guan Xuetao <gxt@...c.pku.edu.cn>
>
> How does this work? UNIFB_MEMSIZE seems to be 4 MB, much more than the
> maximum of 128 KB that kmalloc can allocate.
>
> Shouldn't this use get_free_pages() instead of kmalloc?
>
> Arnd
When using SLUB allocator, if required memory size is larger than 2*PAGE_SIZE, kmalloc_large is called,
and eventually __get_free_pages will be called.
So, it would be the same as __get_free_pages.
--
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