From owner-freebsd-hackers Wed Jul 14 21: 8:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 010C4154D0 for ; Wed, 14 Jul 1999 21:08:35 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA22750; Thu, 15 Jul 1999 13:07:55 +0900 (JST) Message-ID: <378D5C5D.13C65239@newsguy.com> Date: Thu, 15 Jul 1999 12:58:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Jason Thorpe Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) References: <199907142229.PAA02809@lestat.nas.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Thorpe wrote: > > > > ...um, so, make the code that deals with faulting in the stack a bit smarter. > > > > Uh? Like what? Like overcommitting, for instance? The beauty of > > overcommitting is that either you do it or you don't. :-) > > One option is to special-case overcommit the stack. Another is to > set the default stack limits to something more reasonable on a system > where overcommit is disabled. And what do you do, then, with the processes that happen to have legitimate use for more stack? Or maybe you just find out how much stack each process uses, and then set limits appropriate for each one? Which is the equivalent of setting limits to each user, of course... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Would you like to go out with me?" "I'd love to." "Oh, well, n... err... would you?... ahh... huh... what do I do next?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message