Date: Sat, 17 Apr 1999 02:57:05 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: David Schwartz <davids@webmaster.com> Cc: chat@FreeBSD.ORG Subject: Re: swap-related problems Message-ID: <371779F1.7D5C28C2@newsguy.com> References: <000e01be882f$8d6109e0$021d85d1@whenever.youwant.to>
next in thread | previous in thread | raw e-mail | index | archive | help
David Schwartz wrote: > > Not so. As soon as the system has overcommitted by one byte, not a single > 'critical' process will be able to allocate anything. In contrast, > non-critical processes will continue to be able to overcommit. Since we know > the system can remain stable in an overcommit situation (it does so now), > there is no reason to assume that overcommitting will ever have to lead to > any processes being killed. > > So long before critical processes can starve non-critical processes, the > reverse will occur. Ah, I see... you have a kind of point. You will find out, though, that no critical process will run, because the non-critical ones will long have overcommitted. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?371779F1.7D5C28C2>