From: Emmanuel Varagnat <Emmanuel_Varagnat-AEV010@email.mot.com>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Raghava Raju <vraghava_raju@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel stack....
Date: Tue, 11 Sep 2001 12:31:55 +0200 [thread overview]
Message-ID: <3B9DE81B.EA680E13@crm.mot.com> (raw)
In-Reply-To: <20010910214741.19309.qmail@web20008.mail.yahoo.com> <20010910235725.C797@arthur.ubicom.tudelft.nl>
Erik Mouw wrote:
>
> I think you got a wrong understanding of the stack. The stack has no
> separate bss, data, and text sections, it's just a stack of function
> arguments, local variables, and return addresses.
>
> Accessing the stack works automatically: call a function, and the
> function paramaters and the return address are pushed on the stack.
Yes but there is one stack per processor ?
And what about its maximum size ? Is it dynamical ?
-Manu
next prev parent reply other threads:[~2001-09-11 10:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 21:47 Kernel stack Raghava Raju
2001-09-10 21:57 ` Erik Mouw
2001-09-11 10:31 ` Emmanuel Varagnat [this message]
2001-09-11 12:15 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2004-10-13 5:03 Thekkedath, Gopakumar
2004-10-13 4:35 Dhiman, Gaurav
2004-10-14 19:31 ` Denis Vlasenko
2004-10-12 7:51 Thekkedath, Gopakumar
[not found] <577528CFDFEFA643B3324B88812B57FE3055B9@inhyms21.ca.com>
2004-10-12 6:51 ` suthambhara nagaraj
2004-10-12 9:41 ` Jan Hudec
2004-10-12 10:05 ` aq
2004-10-12 10:27 ` Jan Hudec
2004-10-12 12:30 ` aq
2004-10-12 13:11 ` Jan Hudec
2004-10-12 14:30 ` Jon Masters
2004-10-12 14:31 ` Jan Hudec
2004-10-12 6:15 kernel stack suthambhara nagaraj
2004-10-12 11:09 ` Neil Horman
2004-10-13 3:29 ` suthambhara nagaraj
2004-10-14 3:15 ` suthambhara nagaraj
2001-09-11 15:53 Kernel stack Richard J Moore
2001-08-27 22:24 Raghava Raju
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=3B9DE81B.EA680E13@crm.mot.com \
--to=emmanuel_varagnat-aev010@email.mot.com \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=linux-kernel@vger.kernel.org \
--cc=vraghava_raju@yahoo.com \
/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.