From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964791AbXCAKBo (ORCPT ); Thu, 1 Mar 2007 05:01:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964796AbXCAKBo (ORCPT ); Thu, 1 Mar 2007 05:01:44 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:54081 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964791AbXCAKBn (ORCPT ); Thu, 1 Mar 2007 05:01:43 -0500 Date: Thu, 1 Mar 2007 10:54:02 +0100 From: Ingo Molnar To: Evgeniy Polyakov Cc: Pavel Machek , Theodore Tso , Linus Torvalds , Ulrich Drepper , linux-kernel@vger.kernel.org, Arjan van de Ven , Christoph Hellwig , Andrew Morton , Alan Cox , Zach Brown , "David S. Miller" , Suparna Bhattacharya , Davide Libenzi , Jens Axboe , Thomas Gleixner Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 Message-ID: <20070301095402.GA14603@elte.hu> References: <20070226172812.GC22454@2ka.mipt.ru> <20070226195416.GA11188@elte.hu> <20070227102832.GC23170@2ka.mipt.ru> <20070227115221.GJ8154@thunk.org> <20070227121116.GA31597@2ka.mipt.ru> <20070228161413.GA4319@ucw.cz> <20070301081808.GD7217@2ka.mipt.ru> <20070301092634.GB20171@elf.ucw.cz> <20070301094723.GJ7217@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070301094723.GJ7217@2ka.mipt.ru> User-Agent: Mutt/1.4.2.2i X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.0.3 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Evgeniy Polyakov wrote: > I posted kevent/epoll benchmarks and related design issues too many > times both with handmade applications (which might be broken as hell) > and popular open-source servers to repeat them again. numbers are crutial here - and given the epoll bugs in the evserver code that we found, do you have updated evserver benchmark results that compare epoll to kevent? I'm wondering why epoll has half the speed of kevent in those measurements - i suspect some possible benchmarking bug. The queueing model of epoll and kevent is roughly comparable, both do only a constant number of steps to serve one particular request, regardless of how many pending connections/requests there are. What is the CPU utilization of the server system during an epoll test, and what is the CPU utilization during a kevent test? 100% utilized in both cases? Ingo