From owner-freebsd-hackers Tue Aug 7 11:21: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 7081D37B40C; Tue, 7 Aug 2001 11:20:57 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA71224; Tue, 7 Aug 2001 13:29:25 -0700 (PDT) Date: Tue, 7 Aug 2001 13:29:25 -0700 (PDT) From: Julian Elischer To: "Semen A. Ustimenko" Cc: freebsd-hackers@FreeBSD.org Subject: Re: Kernel stack size In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 8 Aug 2001, Semen A. Ustimenko wrote: > Hi! Thanks for light speed response! > > On Tue, 7 Aug 2001, Julian Elischer wrote: > > > the kernel stack is a VERY LIMITED resource > > basically you have about 4 or 5 Kbytes per process. > Oops... And there is no hope to enlarge it? none really. that's the way it is in all kernels.. The kernel is a very limited environment. > > > if you overflow it you write over your signal information.. > > > That's what i'm seeing. SIGPROF, particulary. > > > you should MALLOC space and use a pointer to it.. > > > But this is loss of speed, isn't it? a little but maybe not as much as you think.. malloc is pretty quick. If you are doing it a lot, you might even consider caching the memory blocks.. > > Bye! > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message