On Tue, 2013-01-29 at 09:45 +0800, Alex Shi wrote: > On 01/28/2013 11:47 PM, Mike Galbraith wrote:
> > monteverdi:/abuild/mike/:[0]# echo 1 > /sys/devices/system/cpu/cpufreq/boost > > monteverdi:/abuild/mike/:[0]# massive_intr 10 60 > > 014635 00058160 > > 014633 00058592 > > 014638 00058592 > > 014636 00058160 > > 014632 00058200 > > 014634 00058704 > > 014639 00058704 > > 014641 00058200 > > 014640 00058560 > > 014637 00058560 > > monteverdi:/abuild/mike/:[0]# massive_intr 10 60 > > 014673 00059504 > > 014676 00059504 > > 014674 00059064 > > 014672 00059064 > > 014675 00058560 > > 014671 00058560 > > 014677 00059248 > > 014668 00058864 > > 014669 00059248 > > 014670 00058864 > > monteverdi:/abuild/mike/:[0]# massive_intr 10 60 > > 014686 00043472 > > 014689 00043472 > > 014685 00043760 > > 014690 00043760 > > 014687 00043528 > > 014688 00043528 (hmm) > > 014683 00043216 > > 014692 00043208 > > 014684 00043336 > > 014691 00043336 > > I am sorry Mike. does above 3 times testing has a same sched policy? and > same question for the following testing. Yeah, they're back to back repeats. Using dirt simple massive_intr didn't help clarify aim7 oddity. aim7 is fully repeatable, seems to be saying that consolidation of small independent jobs is a win, that spreading before fully saturated has its price, just as consolidation of large coordinated burst has its price. Seems to cut both ways.. but why not, everything else does. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
