From owner-freebsd-chat Tue May 11 12:27:38 1999 Delivered-To: freebsd-chat@freebsd.org Received: from hades.riverstyx.net (hq-port-89.harbour-dhcp-pool.infinetgroup.com [207.23.37.89]) by hub.freebsd.org (Postfix) with ESMTP id 43182155AE for ; Tue, 11 May 1999 12:27:36 -0700 (PDT) (envelope-from unknown@riverstyx.net) Received: from localhost (unknown@localhost) by hades.riverstyx.net (8.9.3/8.9.3) with ESMTP id MAA27833; Tue, 11 May 1999 12:33:15 -0700 Date: Tue, 11 May 1999 12:33:15 -0700 (PDT) From: To: Dag-Erling Smorgrav Cc: "Daniel O'Connor" , "Jordan K. Hubbard" , chat@FreeBSD.ORG, paul@originative.co.uk Subject: Re: [Re: Request For Better Communications] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pardon my ignorance -- Sioux DoS? Never heard of that one. I'm surprised that they'd actually ignore patches for something that important... --- tani hosokawa river styx internet On 11 May 1999, Dag-Erling Smorgrav wrote: > writes: > > Apache's pool memory seems like a good example, in case anyone cares :) > > It's a good concept, but Apache's implementation of it is very poor - > it leaks like a sieve, and is responsible for making the Sioux DoS > possible. (I offered them patches, which they ignored.) And it's not > real GC - you have to explicitly release a pool to discard the objects > within it, and when you do, *all* objects are discarded, even if > they're still referenced. It works for Apache because they have a lot > of stuff which is transaction-bound - i.e. buffers for reading request > headers, file descriptors to the document or CGI requested, etc., > which can be discarded all in one go. Also, it does more than just GC > since it closes files and sockets does some other cleanup stuff. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message