Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 51889 invoked from network); 9 Dec 2003 16:43:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Dec 2003 16:43:53 -0000 Received: (qmail 23717 invoked by uid 500); 9 Dec 2003 16:43:41 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 23650 invoked by uid 500); 9 Dec 2003 16:43:40 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 23635 invoked from network); 9 Dec 2003 16:43:40 -0000 Received: from unknown (HELO kosh.jetnet.co.uk) (80.87.128.128) by daedalus.apache.org with SMTP; 9 Dec 2003 16:43:40 -0000 Received: from goliath (host81-128-10-126.in-addr.btopenworld.com [81.128.10.126]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 522A022937; Tue, 9 Dec 2003 16:43:43 +0000 (GMT) Message-ID: <00e701c3be73$be1acdd0$7500a8c0@goliath> From: "David Reid" To: , References: <3FD5E723.9020706@attglobal.net> Subject: Re: Apache MPMs comparing new fds with FD_SETSIZE, APR's ability to wait for i/o on socket Date: Tue, 9 Dec 2003 16:44:41 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > Currently when Apache httpd accepts a new connection via APR, it compares the > fd with FD_SETSIZE and bombs if fd >= FD_SETSIZE. > > The limited value of this check is on platforms such as OS X < 10.3 with no > poll(), where APR has to use select(). Unfortunately, use 1K threads with > worker MPM on Solaris or some other platform with relatively small *default* > FD_SETSIZE and you'll start hitting meaningless FD_SETSIZE errors before you > get the 1K threads busy talking to clients. (APR doesn't use select() on > Solaris anyway, so the FD_SETSIZE check is not helpful.) > > For APR 1.0, I think it would be better for APR to handle this to the greatest > extent so that APR apps don't have to worry about whether or not APR uses select(). This seems entirely sensible :) david