linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hagen Paul Pfeifer <hpplinuxml@0xdef.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 128 kbytes allocation limit for kmalloc?
Date: Wed, 28 Sep 2005 14:55:09 +0200	[thread overview]
Message-ID: <20050928125509.GA28656@0xdef.net> (raw)
In-Reply-To: <20050927174032.GA26236@archivum.info>

* mailarch@archivum.info | 2005-09-27 19:40:32 [+0200]:

>Hello,
>
>is it possible to allocate more than 128 kbytes in a kernel lkm module?

Yes, multiple kmalloc calls. You can implement your own memory managment
in top of it. For further informations: cat /proc/slabinfo

>When I allocate more than 128 kbytes with the kmalloc call, kmalloc returns NULL.

If you need one continues chunk of memory you must take vmalloc. But
note the performance penalty and some other disadvantages (dma, ...).

HGN

-- 
Standards are industry's way of codifying obsolescence.

      parent reply	other threads:[~2005-09-28 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 17:40 128 kbytes allocation limit for kmalloc? mailarch
2005-09-27 17:49 ` Brian Gerst
2005-09-28 12:55 ` Hagen Paul Pfeifer [this message]

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=20050928125509.GA28656@0xdef.net \
    --to=hpplinuxml@0xdef.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).