Date: Wed, 29 Nov 2006 22:50:25 +0000 From: John Birrell <jb@what-creek.com> To: Scott Long <scottl@samsco.org> Cc: Rene Ladan <r.c.ladan@gmail.com>, jb@freebsd.org, freebsd-current@freebsd.org Subject: Re: calcru-triggered panic? Message-ID: <20061129225025.GA584@what-creek.com> In-Reply-To: <456E0C66.4060404@samsco.org> References: <45622068.2050705@student.tue.nl> <200611291204.03716.jhb@freebsd.org> <20061129223221.GA359@what-creek.com> <456E0C66.4060404@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 29, 2006 at 03:40:38PM -0700, Scott Long wrote: > It's probably less of an issue now that it used to be, since I/O is > decoupled through GEOM threads. In 4.x, you could have a stack that > went from the syscall, through VFS, UFS, the block layer, CAM, and > finally the device driver. When I was working on RAIDFrame, adding > just a couple hundred bytes of stack usage would cause it to blow out. > But as I said, it might not be as much of an issue now. Is it possible to check how deep the stack is and avoid using a stack buffer if too deep? -- John Birrell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061129225025.GA584>