[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070226193054.GB17892@2ka.mipt.ru>
Date: Mon, 26 Feb 2007 22:30:59 +0300
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Ingo Molnar <mingo@...e.hu>, 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
On Mon, Feb 26, 2007 at 11:22:46AM -0800, Linus Torvalds (torvalds@...ux-foundation.org) wrote:
> See? Stop blathering about how everything is an event. THAT'S NOT
> RELEVANT. I've told you a hundred times - they may be "logically
> equivalent", but that doesn't change ANYTHING. Event-based programming
> simply isn't suitable for 99% of all stuff, and for the 1% where it *is*
> suitable, it actually tends to be a very specific subset of the code that
> you actually use events for (ie accept and read/write on pure streams).
Will you argue that people do things like
num = epoll_wait()
for (i=0; i<num; ++i) {
process(event[i])?
}
Will you spawn thread per IO?
Stop writing the same again and again - I perfectly understand that not
everything can be easily covered by events, but covering everything with
threads is more stupid idea.
High-performance IO requires as small as possible overhead, dispatching
events from ring buffer or queue from each cpu is the smallest one, but
not spawning a thread per read.
> Linus
--
Evgeniy Polyakov
-
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