public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] kmalloc() and page sizes
Date: Fri, 11 Jan 2002 12:09:11 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805809@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805788@msgid-missing>

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 <christian.hildner@hob.de> 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



  parent reply	other threads:[~2002-01-11 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 10:18 [Linux-ia64] kmalloc() and page sizes Christian Hildner
2002-01-10 19:56 ` David Mosberger
2002-01-11 12:09 ` Christian Hildner [this message]
2002-01-11 16:38 ` David Mosberger

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=marc-linux-ia64-105590698805809@msgid-missing \
    --to=christian.hildner@hob.de \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox