From: ooyama eiichi <ooyama@tritech.co.jp>
To: cw@f00f.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel stack size
Date: Sun, 03 Apr 2005 03:48:58 +0900 (JST) [thread overview]
Message-ID: <20050403.034858.70218818.ooyama@tritech.co.jp> (raw)
In-Reply-To: <20050402182438.GA29095@taniwha.stupidest.org>
> On Sun, Apr 03, 2005 at 03:15:42AM +0900, ooyama eiichi wrote:
>
> > in i386 and ia64.
>
> search for CONFIG_DEBUG_STACKOVERFLOW in arch/i386/kernel/irq.c
Oh, very good information for me.
>
> ia64 has fairly large stacks so you probably won't need to check there
> if you get the above working
in ia64, he works properly.
>
> > because my driver hungs the machine by an certain ioctl. and it
> > seems to me there is no bad in the code correspond to the ioctl,
> > except for that it is using large auto variables. (some functions
> > are useing ~1KB autos)
>
> don't do that, even if you make it 'apparently' work for you it will
> just end up being a problem mater on or for someone else
>
I changed these to using kmalloc().
(but not yet confirmed for my driver to work properly)
Thanks very much.
next prev parent reply other threads:[~2005-04-02 18:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 17:46 ooyama eiichi
2005-04-02 17:53 ` Chris Wedgwood
2005-04-02 18:15 ` ooyama eiichi
2005-04-02 18:24 ` Chris Wedgwood
2005-04-02 18:48 ` ooyama eiichi [this message]
2005-04-02 19:04 ` Steven Rostedt
2005-04-02 19:37 ` Al Viro
2005-04-02 19:52 ` Steven Rostedt
2005-04-02 18:29 ` Brian Gerst
-- strict thread matches above, loose matches on Subject: below --
2005-04-02 20:14 Manfred Spraul
2005-04-02 22:15 ` Steven Rostedt
2005-04-03 7:10 ` Manfred Spraul
2005-04-03 18:01 ` Steven Rostedt
2005-04-03 19:23 ` Manfred Spraul
2003-10-09 19:14 Punj, Arun
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=20050403.034858.70218818.ooyama@tritech.co.jp \
--to=ooyama@tritech.co.jp \
--cc=cw@f00f.org \
--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
all inboxes | Powered by JetHome®