public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: ooyama eiichi <ooyama@tritech.co.jp>
Cc: cw@f00f.org, linux-kernel@vger.kernel.org
Subject: Re: kernel stack size
Date: Sat, 02 Apr 2005 13:29:29 -0500	[thread overview]
Message-ID: <424EE489.4040900@didntduck.org> (raw)
In-Reply-To: <20050403.031542.23015132.ooyama@tritech.co.jp>

ooyama eiichi wrote:
> Thanks for your reply.
> 
> 
>>On Sun, Apr 03, 2005 at 02:46:34AM +0900, ooyama eiichi wrote:
>>
>>
>>>How can I know the rest size of the kernel stack.
>>
>>you can't in a platfork-independant way
> 
> 
> in i386 and ia64.
> 
> 
>>>(in my kernel driver)
>>
>>*why* do you want to do this?
>>
> 
> 
> 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)

That's your problem.  Use kmalloc instead of large local variables.

--
				Brian Gerst

  parent reply	other threads:[~2005-04-02 18:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02 17:46 kernel stack size 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
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 [this message]
  -- 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=424EE489.4040900@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ooyama@tritech.co.jp \
    /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