linux-kernel - Re: [tip:sched/core] sched: Untangle cpu-load and timekeeping code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Jan 2011 14:55:30 +0800
From:	Yong Zhang <yong.zhang0@...il.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, mingo@...e.hu,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched: Untangle cpu-load and timekeeping code

On Thu, Jan 27, 2011 at 4:03 AM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
>> We should not do this checking any more. In normal case,
>> it will always return false.
>> If it indeed returns true for some reason, we will lose the
>> timer forever.
>
> Its needed for the nohz case, arguably we could move it inside
> calc_global_nohz().

I have no idea why we need that checking in  calc_global_nohz().

Before this patch, time_before(jiffies, calc_load_update) is
needed in calc_global_nohz() because it will reduce the ovehead
on dealing with calc_load_fold_idle if we have idle dance in one
LOAD_FREQ.

Now we have calc_global_load() called at every LOAD_FREQ
instead of every tick, that problem is gone.

But maybe I have missed something ;)

Thanks,
Yong


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