[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070530083254.GA21528@2ka.mipt.ru>
Date: Wed, 30 May 2007 12:32:54 +0400
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Ingo Molnar <mingo@...e.hu>
Cc: Jeff Garzik <jeff@...zik.org>, Zach Brown <zach.brown@...cle.com>,
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>,
"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: Syslets, Threadlets, generic AIO support, v6
Hi Ingo, developers.
On Wed, May 30, 2007 at 09:20:55AM +0200, Ingo Molnar (mingo@...e.hu) wrote:
>
> * Jeff Garzik <jeff@...zik.org> wrote:
>
> > You should pick up the kevent work :)
>
> 3 months ago i verified the published kevent vs. epoll benchmark and
> found that benchmark to be fatally flawed. When i redid it properly
> kevent showed no significant advantage over epoll. Note that i did those
> measurements _before_ the recent round of epoll speedups. So unless
> someone does believable benchmarks i consider kevent an over-hyped,
> mis-benchmarked complication to do something that epoll is perfectly
> capable of doing.
I did not want to start with another round of ping-pong insults :), but,
Ingo, you did not show that kevent works worse. I did show that
sometimes it works better. It flawed from 0 to 30% win in that tests,
in results Johann Bork presented kevent and epoll behaved the same. In
results I posted earlier, I said, that sometimes epoll behaved better,
sometimes kevent. What does it say? Just the fact, that in that given
workload result was the one we saw. Nothing more, nothing less.
It does not show something is broken, and definitely not that it is:
citation1:
we're heading to yet-another monolitic interface, we're heading with no
valid reasons given if other than some handwaving.
citation2:
consider kevent an over-hyped, mis-benchmarked complication to do
something that epoll is perfectly
Getting into account another features kevent has (and what it was
designed for originally - for network AIO, which is quite hard
(if ever possible) with files and epoll, I'm not talking about syslets
as AIO, it is different approach and likely it is simpler, getting even
only that it is already very good), it is not what people said in above
citations.
It looks like you have some personal insults on that, which I do not
understand. But it has nothing with technical side of the problem, so
lets stop such rethoric and concentrate on real problem and forget any
possible personal issues which might be raised sometimes :).
Although I closed kevent and eventfs projects, I would gladly continue
if we can and want to have progress in that area.
Thanks.
> 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