From: Dan Malek <dan@embeddededge.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "David C. Chiu" <dchiu@ariodata.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Enlarging Kernel Stack (doesn't this question ever go away?)
Date: Mon, 24 Jun 2002 18:05:57 -0400 [thread overview]
Message-ID: <3D1797C5.8080808@embeddededge.com> (raw)
In-Reply-To: 20020624214255.GK3489@opus.bloom.county
Tom Rini wrote:
> Why are you trying to enlarge the stack? This question never goes away
> since it's almost always wrong to enlarge the stack...
That's correct......you should be allocating space with vmalloc() and
just hanging on to a pointer that you vfree() later.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-24 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 20:50 Enlarging Kernel Stack (doesn't this question ever go away?) David C. Chiu
2002-06-24 21:42 ` Tom Rini
2002-06-24 22:05 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 22:11 David C. Chiu
2002-06-24 22:28 ` Dan Malek
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=3D1797C5.8080808@embeddededge.com \
--to=dan@embeddededge.com \
--cc=dchiu@ariodata.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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.