From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Hildner Date: Fri, 11 Jan 2002 12:09:11 +0000 Subject: Re: [Linux-ia64] kmalloc() and page sizes Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-ia64@vger.kernel.org David, the storage I need for my driver has to be mapped by the 64MB kernel page. The alloc_pages() gives me pages with virtual addresses outside the kernel mapped page. Since kmalloc() gives storage at natural alignment this call is perfect to overlay the storage with an additional mapping with 256KB page size. Christian David Mosberger schrieb: > >>>>> On Thu, 10 Jan 2002 11:18:49 +0100, Christian Hildner said: > > Christian> Hi all! In the current kernels the size limit for > Christian> kmalloc() is 128KB. The ia64 architecture provides > Christian> pagesizes ranging from 4K, ... , 64K, 256K, ... , 4G. If > Christian> we would increase the maximum kmalloc() size limit to > Christian> 256K (or 1M) this would match perfectly to the pagesizes. > > Christian> Since I need a large (256K) segment from kmalloc(), I > Christian> would appreciate the increase of the size limit. Maybe > Christian> also other 64Bit architectures could benefit from that. > > Christian> Please tell your opinion to the list. > > Is there a reason you can't use alloc_pages() directly? It can handle > allocation orders of up to 10 (not that you'll find many chunks of > that size!). The slab allocator is limited to an allocation order of > 5, as you observed. > > --david