From: Arnd Bergmann <arnd@arndb.de>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: 'Paul Mundt' <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] unicore32 framebuffer driver fix: make videomemory kmalloc-ed and floatable
Date: Wed, 30 Mar 2011 10:55:18 +0000 [thread overview]
Message-ID: <201103301255.18551.arnd@arndb.de> (raw)
In-Reply-To: <01ea01cbeeb6$99bb5240$cd31f6c0$@mprc.pku.edu.cn>
On Wednesday 30 March 2011, Guan Xuetao wrote:
> Is it appropriate to using __get_free_pages in framebuffer driver?
Yes, it is appropriate, and it is also more efficient than using
kmalloc.
> And both SLAB and SLUB allocators support 4MB request.
Ok, I did not know that, but I see now how the maximum size is computed.
The limit was 128 KB for a long time, but has apparently changed.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "Guan Xuetao" <gxt@mprc.pku.edu.cn>
Cc: "'Paul Mundt'" <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] unicore32 framebuffer driver fix: make videomemory kmalloc-ed and floatable
Date: Wed, 30 Mar 2011 12:55:18 +0200 [thread overview]
Message-ID: <201103301255.18551.arnd@arndb.de> (raw)
In-Reply-To: <01ea01cbeeb6$99bb5240$cd31f6c0$@mprc.pku.edu.cn>
On Wednesday 30 March 2011, Guan Xuetao wrote:
> Is it appropriate to using __get_free_pages in framebuffer driver?
Yes, it is appropriate, and it is also more efficient than using
kmalloc.
> And both SLAB and SLUB allocators support 4MB request.
Ok, I did not know that, but I see now how the maximum size is computed.
The limit was 128 KB for a long time, but has apparently changed.
Arnd
next prev parent reply other threads:[~2011-03-30 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 14:37 [PATCH] unicore32 framebuffer driver fix: make videomemory kmalloc-ed and floatable Guan Xuetao
2011-03-29 14:37 ` Guan Xuetao
2011-03-29 14:42 ` Arnd Bergmann
2011-03-29 14:42 ` Arnd Bergmann
2011-03-29 14:54 ` Guan Xuetao
2011-03-29 14:54 ` Guan Xuetao
2011-03-30 1:39 ` Guan Xuetao
2011-03-30 1:39 ` Guan Xuetao
2011-03-30 6:54 ` Arnd Bergmann
2011-03-30 6:54 ` Arnd Bergmann
2011-03-30 8:43 ` Guan Xuetao
2011-03-30 8:43 ` Guan Xuetao
2011-03-30 10:55 ` Arnd Bergmann [this message]
2011-03-30 10:55 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201103301255.18551.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gxt@mprc.pku.edu.cn \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.