[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070227131427.GA29798@2ka.mipt.ru>
Date: Tue, 27 Feb 2007 16:14:29 +0300
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Ingo Molnar <mingo@...e.hu>
Cc: 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
On Tue, Feb 27, 2007 at 01:34:21PM +0100, Ingo Molnar (mingo@...e.hu) wrote:
> based servers. The measurements so far have shown that the absolute
> worst-case threading server performance is at around 60% of that of
> non-context-switching servers - and even that level is reached
> gradually, leaving time for action for the server owner. While with
> fully event based servers there are mostly only two modes of
> performance: 100% performance and near-0% performance: total breakdown.
Let's live in piece! :)
I always agreed that they should be used together - event-based rings
of IO requests, if request happens to block (which should be avaided
as much as possible), then it continues on behalf of sleeping thread.
> Ingo
--
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