[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070301101924.GB14603@elte.hu>
Date: Thu, 1 Mar 2007 11:19:24 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Pavel Machek <pavel@....cz>
Cc: Evgeniy Polyakov <johnpol@....mipt.ru>,
Theodore Tso <tytso@....edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ulrich Drepper <drepper@...hat.com>,
linux-kernel@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@....com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Zach Brown <zach.brown@...cle.com>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Davide Libenzi <davidel@...ilserver.org>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
* Pavel Machek <pavel@....cz> wrote:
> > Threadlets behave much worse without event driven model, events can
> > behave worse without backed threads, they are mutually compensating.
>
> I think Ingo demonstrated unoptimized threadlets to be within 5% to
> the speed of kevent. [...]
that was epoll not kevent, but yeah. To me the biggest question is, how
much improvement does kevent bring relative to epoll? Epoll is a pretty
good event queueing API, and it covers all the event sources today. It
is also O(1) throughout, so i dont really understand how it could only
achieve half the speed of kevent in the evserver_epoll/kevent.c
benchmark. We need to understand that first.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists