Re: [PATCH] Track accurate idle time with tick_sched.idle_sleeptime

Venki Pallipadi <[email protected]> writes:
>  
> +void tick_nohz_stop_idle(int cpu)
> +{
> +	struct tick_sched *ts = &per_cpu(tick_cpu_sched, cpu);
> +
> +	if (ts->idle_active) {
> +		ktime_t now, delta;
> +		now = ktime_get();

That could be PM timer read costing thousands of cycles.

For going into idle it's probably not a real problem, but it could
seriously affect out of idle latencies.

You would really need a cheaper per CPU timer that doesn't
stop in idle (which rules out sched_clock). It's all unfortunately
quite messy.

-Andi
-
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/

---

• Follow-Ups:
  • Re: [PATCH] Track accurate idle time with tick_sched.idle_sleeptime
    • From: Ingo Molnar <[email protected]>

• References:
  • [PATCH] Track accurate idle time with tick_sched.idle_sleeptime
    • From: Venki Pallipadi <[email protected]>

• Prev by Date: Re: speeding up swapoff
• Next by Date: Re: [PATCH] x86/x86-64 PCI domain support
• Previous by thread: RE: [PATCH] Track accurate idle time with tick_sched.idle_sleeptime
• Next by thread: Re: [PATCH] Track accurate idle time with tick_sched.idle_sleeptime
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]