From owner-freebsd-hackers Tue Feb 19 9:53:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from host213-123-131-110.in-addr.btopenworld.com (host213-123-131-110.in-addr.btopenworld.com [213.123.131.110]) by hub.freebsd.org (Postfix) with ESMTP id 596CD37B405 for ; Tue, 19 Feb 2002 09:53:51 -0800 (PST) Received: by host213-123-131-110.in-addr.btopenworld.com (Postfix, from userid 1001) id DE191542; Tue, 19 Feb 2002 17:54:31 +0000 (GMT) Date: Tue, 19 Feb 2002 17:54:31 +0000 From: Dominic Marks To: Kip Macy Cc: Peter Wemm , Mike Silbersack , Hiten Pandya , freebsd-hackers@FreeBSD.ORG Subject: Re: In-Kernel HTTP Server (name preference) Message-ID: <20020219175431.A12535@host213-123-131-110.in-addr.bto> References: <20020219092058.A78717@host213-123-131-110.in-addr.bto> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from kmacy@netapp.com on Tue, Feb 19, 2002 at 09:19:56AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, On Tue, Feb 19, 2002 at 09:19:56AM -0800, Kip Macy wrote: > > Apache will switch to this method at some point. I really can't > > understand why they went with that complicated pre-forking stuff. > > Using non-blockijng I/O is just not that hard." > > As mentioned previously, due to the blocking semantics of file I/O on unix, > single process servers will only provide peak throughput if everything is > resident. By pre-forking, data can continued to be served if one process blocks > on file I/O. Apache already handles multiple connections within a process, so > it does something like this already. Yes.. but if your using non-blocking IO for both the disc and network read/writes, this no longer applies. If I understand correctly in normal operation a server like tHttpd simply blocks on kevent() and when a descriptor becomes available for servicing it handles this occurance, or occurances since a single kevent() call can return more than a single event and then goes back to blocking. Reads and writes don't block if they don't complete, you simply get another event when the descriptor becomes available again. Am I wrong? > -Kip > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message