From owner-freebsd-current Mon Apr 3 6:21:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 939D337BDDB for ; Mon, 3 Apr 2000 06:21:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA21187; Mon, 3 Apr 2000 15:20:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: hm@hcs.de Cc: garyj@muc.de, bright@wintelcom.net, freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-reply-to: Your message of "Mon, 03 Apr 2000 15:17:57 +0200." <20000403131757.4F48238FA@hcswork.hcs.de> Date: Mon, 03 Apr 2000 15:20:57 +0200 Message-ID: <21185.954768057@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000403131757.4F48238FA@hcswork.hcs.de>, Hellmuth Michaelis writes : >>From the keyboard of Poul-Henning Kamp: > >> We need to be frugal about the kernel stack, for a lot of reasons, >> that's just the way it is, and as far as I know it is the way >> it will continue to be. > >Good. I'd like to learn something from it: Shall i avoid allocating >structs on the kernel stack at all or is it just bad to allocate >big structs ? My own rule of thumb is "about 60 bytes or so", but it also depends on the lifetime of the function. If it is a leaf function which doesn't call anything else I'll let it use more stack, if it is a function which is burried at the bottom (top really) of the stack all the time I'm less tolerant. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message