From owner-freebsd-hackers Tue Jul 13 20: 7:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 403211538B; Tue, 13 Jul 1999 20:07:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA86009; Tue, 13 Jul 1999 20:06:11 -0700 (PDT) (envelope-from dillon) Date: Tue, 13 Jul 1999 20:06:11 -0700 (PDT) From: Matthew Dillon Message-Id: <199907140306.UAA86009@apollo.backplane.com> To: David Greenman Cc: "Charles M. Hannum" , Noriyuki Soda , Jason Thorpe , "Brian F. Feldman" , bright@rush.net, dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, jon@oaktree.co.uk, tech-userlevel@netbsd.org Subject: Re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) References: <199907140225.TAA14312@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I've long felt that the best solution to problems like this is a per-user :swap space quota. This gives admins a knob to manage the allocation of swap :space while still allowing overcommit. The downside is that it doesn't provide :a graceful way for a program to recover from it's overconsumption sins. I'd :argue, however, that buggy software or incorrectly tuned systems should get :what they deserve. : :-DG : :David Greenman Ooh, cool idea. If I had that at BEST I would use it snap! like that! A per-user swap quota would work a whole lot better then the current numprocs x datasize limit -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message