* Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

quoted text
> >>cool. It's already upstream (post-rc3 commit):
> [YM] But comparing with 2.6.26, volanoMark result still has about 60%
> regression.

Does a scheduler trace show anything about why that drop happens? Do 
something like this to trace the scheduler:

assuming debugfs is mounted under /debug and CONFIG_SCHED_TRACER=y:

  echo 1 > /debug/tracing/tracing_cpumask
  echo sched_switch > /debug/tracing/available_tracers
  cat /debug/tracing/trace_pipe > trace.txt

( regarding tracing_cpumask: trace only 1 CPU to make sure volanomark is 
  not disturbed too much by many-CPUs tracing. )

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/