From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 114ED1F461; Tue, 25 Jun 2019 06:41:02 +0000 (UTC) Date: Tue, 25 Jun 2019 06:41:01 +0000 From: Eric Wong To: meta@public-inbox.org Subject: Re: [PATCH] listener: support publicinboxdaemon.multiaccept in config Message-ID: <20190625064101.iwif2x6l2t6alhre@dcvr> References: <20190513025610.30378-1-e@80x24.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190513025610.30378-1-e@80x24.org> List-Id: Eric Wong wrote: > Similar to the nginx "multi_accept" parameter, this allows > single-worker deployments to accept() multiple clients whenever > the listen socket reports readiness via epoll_wait/poll/kevent. > > Unlike nginx, we also parse an integer parameter to determine > how many times in a row we call accept(). Given the ability to have per-listener cert/key options(*) for OpenSSL, I think this parameter should be per-listener, too; and thus specified in the command-line. (*) which reminds me, I still need to write tests and document that...