The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortel.com>
To: cranium2003 <cranium2003@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel memory usage any restrictions?
Date: Fri, 27 May 2005 12:46:40 -0600	[thread overview]
Message-ID: <42976B10.5030101@nortel.com> (raw)
In-Reply-To: <20050527181851.69524.qmail@web33008.mail.mud.yahoo.com>

cranium2003 wrote:
> hello,
>               Is there any restricition on using
> kernel's memory? also if i require to use some kernel
> memory say 625kB by allocating that in GFP_ATOMIC mode

Your call will almost certainly fail.  I think kmalloc will only give 
you up to 128KB, and even that might be tricky to do with GFP_ATOMIC.

For larger chunks of memory, you can use vmalloc() or reserve it 
statically at compile time.

Chris

  reply	other threads:[~2005-05-27 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 18:18 kernel memory usage any restrictions? cranium2003
2005-05-27 18:46 ` Chris Friesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-28  1:56 cranium2003
2005-05-28  2:16 ` Steven Rostedt

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=42976B10.5030101@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=cranium2003@yahoo.com \
    --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