20 Aug 09:24
Re: VolanoMark regression with 2.6.27-rc1
From: Zhang, Yanmin <yanmin_zhang <at> linux.intel.com>
Subject: Re: VolanoMark regression with 2.6.27-rc1
Newsgroups: gmane.linux.kernel
Date: 2008-08-20 07:24:49 GMT
Subject: Re: VolanoMark regression with 2.6.27-rc1
Newsgroups: gmane.linux.kernel
Date: 2008-08-20 07:24:49 GMT
On Mon, 2008-08-18 at 10:51 +0530, Dhaval Giani wrote: > > > > > > So with kernel 2.6.27-rc1, the successful wakeup_affine is about > > > > > > double of the one of 2.6.27-rc1 > > > > > > on domain 0, but about 10 times on domain 1. That means more tasks are > > > > > > woken up on waker cpus. > > > > > > > > > > > > Does that mean it doesn't follow cache-hot checking? > > > > > > > > > > I'm a bit puzzled, but you're right - I too noticed that volanomark is > > > > > _very_ sensitive to affine wakeups. > > > > > > > > > > I'll try and find what changed in that code for GROUP=n. > > > > > > > > hi Yanmin, > > > > > > > > I was wondering if you could send me your config and what sysctls you > > > > have set. I have not been able to reproduce the 2.6.26 -> 2.6.27-rc1 > > > > GROUP=n regression. > > > Pls. see the attachment. As for sysctl, I just set /proc/sys/kernel/sched_compat_yield=1. > > > > > > I am wondering if the load balance causes the regression when group=n. I manually delete > > > all GROUP codes and do a diff against 26 and 27-rc1. > > > > > > > You can disable load balancing by being in uniprocessor mode. > > > > Hi, >(Continue reading)
Ingo
>
> > > + (void) (&_avg1 == &_avg2); \
> > > + _avg1 + _avg2; })
I don't think this implementation of avg should go in kernel.h?
It gives an average of 1 and 1 to be 2, 3 and 3 is 4, 1 and 3 is
3 etc.
Maybe it is reasonable for very high numbers that would overflow
if added first, but it doesn't seem reasonable for a generic
averaging function.
RSS Feed