On Thu, Mar 01, 2007 at 12:28:00PM +0100, Eric Dumazet ([EMAIL PROTECTED]) wrote: > On Thursday 01 March 2007 12:20, Evgeniy Polyakov wrote: > > On Thu, Mar 01, 2007 at 12:14:44PM +0100, Eric Dumazet ([EMAIL PROTECTED]) > wrote: > > > On Thursday 01 March 2007 11:59, Evgeniy Polyakov wrote: > > > > Yes, it is about 98-100% in both cases. > > > > I've just re-run tests on my amd64 test machine without debug options: > > > > > > > > epoll 4794.23 > > > > kevent 6468.95 > > > > > > It would be valuable if you could post oprofile results > > > (CPU_CLK_UNHALTED) for both tests. > > > > I can't - oprofile does not work on this x86_64 machine: > > > > Yes, this is a known problem, but you can make it works, as I did. > > Please :)
I can not resist :) > I used the CVS version of oprofile plus a patch you can find in the mailing > list archives. Dont remember exactly, since I hit this some months ago Could you provide at least remote way to find it? I only found the same problem at http://lkml.org/lkml/2006/10/27/3 but without any hits to solve the problem. I will try CVS oprofile, if it works I will provide details of course. My tree is based on rc1 and has this latest commit: commit b5bf28cde894b3bb3bd25c13a7647020562f9ea0 Author: Linus Torvalds <[EMAIL PROTECTED]> Date: Wed Feb 21 11:21:44 2007 -0800 There are no commits after that data with word 'oprofile' in git-whatchanged at least. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
