All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: cranium2003 <cranium2003@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Chris Friesen <cfriesen@nortel.com>
Subject: Re: kernel memory usage any restrictions?
Date: Fri, 27 May 2005 22:16:33 -0400	[thread overview]
Message-ID: <1117246593.6477.43.camel@localhost.localdomain> (raw)
In-Reply-To: <20050528015650.75229.qmail@web33001.mail.mud.yahoo.com>

On Fri, 2005-05-27 at 18:56 -0700, cranium2003 wrote:

> > 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.
> > 
>          NO I mean the source code total require 625kB
> not i require a single call of kmalloc with GFP_ATOMIC
> but many calls whose total sum will be around 625kB.

Matters what you system is.  I have a gig of RAM and can easily allocate
a meg by 32 32K chunks.  I haven't tried it with ATOMIC, but that just
means it will fail if it can't get you something right away and it needs
to sleep.  But if you keep trying, that is, don't allocate then
(assuming you're in an interrupt) and try again another time (in another
interrupt), you should eventually get the 625kB.  But as this answer is,
you need to supply more context.  If you can't fail any of those tries,
then it probably won't work.  You're system may be cached out, and would
need to write pages to the disk before it can give you the memory you
need, and then it would have to sleep.

-- Steve



  reply	other threads:[~2005-05-28  2:16 UTC|newest]

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

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=1117246593.6477.43.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=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 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.