From owner-freebsd-hackers Fri Feb 22 8:11:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 754E937B404 for ; Fri, 22 Feb 2002 08:11:12 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 52D08AE2C3; Fri, 22 Feb 2002 08:11:12 -0800 (PST) Date: Fri, 22 Feb 2002 08:11:12 -0800 From: Alfred Perlstein To: J Turner Cc: freebsd-hackers@freebsd.org Subject: Re: In-Kernel HTTP Server (name preference) Message-ID: <20020222161112.GL12136@elvis.mu.org> References: <20020219092058.A78717@host213-123-131-110.in-addr.bto> <20020219175431.A12535@host213-123-131-110.in-addr.bto> <20020219180004.GO12136@elvis.mu.org> <20020221185354.A50908@stan.jamwt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221185354.A50908@stan.jamwt.com> User-Agent: Mutt/1.3.27i 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 Why would you reply to me but not include me in the CC? * J Turner [020221 18:53] wrote: > On Tue, Feb 19, 2002 at 10:00:04AM -0800, Alfred Perlstein wrote: > > Disk IO can't be done in a non-blocking manner. If the kernel doesn't > > have the portion of the file you wish to read in the buffer cache > > then the process will block waiting. > > Isn't this exactly what the kqueue mechanism circumvents? No, neither poll(2), kqueue(2) nor most filesystems have mechanism doing async IO without using heavyweight processes. (however this is on the verge of being fixed via Julian's KSE work) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message