[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070226125123.GA31357@elte.hu>
Date: Mon, 26 Feb 2007 13:51:23 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Evgeniy Polyakov <johnpol@....mipt.ru>
Cc: Davide Libenzi <davidel@...ilserver.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.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>,
Ulrich Drepper <drepper@...hat.com>,
Zach Brown <zach.brown@...cle.com>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
* Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> Even having main dispatcher as epoll/kevent loop, the _whole_
> threadlet model is absolutely micro-thread in nature and not state
> machine/event.
Evgeniy, i'm not sure how many different ways to tell this to you, but
you are not listening, you are not learning and you are still not
getting it at all.
The scheduler /IS/ a generic work/event queue. And it's pretty damn
fast. No amount of badmouthing will change that basic fact. Not exactly
as fast as a special-purpose queueing system (for all the reasons i
outlined to you, and which you ignored), but it gets pretty damn close
even for the web workload /you/ identified, and offers a user-space
programming model that is about 1000 times more useful than
state-machines.
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