kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Recursive function in Kernel space
Date: Wed, 22 Dec 2010 20:50:59 +0700	[thread overview]
Message-ID: <AANLkTikSqiyzFDnWEqG+-97U_BQyOET=x+AFKhH8R1dS@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=+ofvxuADMFpz9veJd4POsjL8N=LLkzfbA8XO4@mail.gmail.com>

On Wed, Dec 22, 2010 at 13:02, Darshan Ghumare
<darshan.ghumare@gmail.com> wrote:
>
> Sir,
> I have following question,
> Why recursive function is not recommended in Kernel-Space?


because kernel stack is limited...about 8K...or 4K if you choose to
have such amount...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

           reply	other threads:[~2010-12-22 13:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <AANLkTi=+ofvxuADMFpz9veJd4POsjL8N=LLkzfbA8XO4@mail.gmail.com>]

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='AANLkTikSqiyzFDnWEqG+-97U_BQyOET=x+AFKhH8R1dS@mail.gmail.com' \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).