Date: Wed, 12 May 1999 18:04:57 +0200 From: Pierre Beyssac <beyssac@enst.fr> To: Stefan Bethke <stefan.bethke@hanse.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: mbuf starvation Message-ID: <19990512180457.A2829@enst.fr> In-Reply-To: <803947.3135519807@d225.promo.de>; from Stefan Bethke on Wed, May 12, 1999 at 05:43:27PM %2B0200 References: <19990512172544.A440@enst.fr> <803947.3135519807@d225.promo.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 12, 1999 at 05:43:27PM +0200, Stefan Bethke wrote: > I've discussed this with Garett back in September. The reason is quite > simple: unless all cases of not checking for a NULL pointer returned are > fixed (or instrumented with a panic), it is better to fail with a panic > than with some obscure problem later on. Yes, I would agree in the general case, but in that particular case the reasonning is flawed: you panic every time, while there are many cases that currently are handled gracefully by the caller. In other words, you don't leave any choice to the caller. That's bad. IHMO it's not even a good thing in general because mbuf starvations can and _will_ happen as a normal condition, not because of bugs but because of high resource use. It can have its uses for debugging purposes, as a compilation option. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990512180457.A2829>