From: Brian Gerst <bgerst@didntduck.org>
To: mailarch@archivum.info
Cc: linux-kernel@vger.kernel.org
Subject: Re: 128 kbytes allocation limit for kmalloc?
Date: Tue, 27 Sep 2005 13:49:47 -0400 [thread overview]
Message-ID: <4339863B.2080905@didntduck.org> (raw)
In-Reply-To: <20050927174032.GA26236@archivum.info>
mailarch@archivum.info wrote:
> Hello,
>
> is it possible to allocate more than 128 kbytes in a kernel lkm module?
> When I allocate more than 128 kbytes with the kmalloc call, kmalloc returns NULL.
>
No. Use vmalloc(). Keep in mind that kernel memory is a limited
resource, so don't use more memory that you really have to.
--
Brian Gerst
next prev parent reply other threads:[~2005-09-27 17:48 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 [this message]
2005-09-28 12:55 ` Hagen Paul Pfeifer
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=4339863B.2080905@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailarch@archivum.info \
/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.