linux-kernel - Re: [PATCH v1] sched: fix nohz idle load balancer issues

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:	Wed, 28 Sep 2011 10:36:58 +0530
From:	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
To:	Venki Pallipadi <venki@...gle.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Turner <pjt@...gle.com>, Ingo Molnar <mingo@...e.hu>,
	Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] sched: fix nohz idle load balancer issues

* Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com> [2011-09-28 10:09:21]:

> * Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com> [2011-09-28 10:04:27]:
> 
> > unless we want to go for more sophisticated like a sorted list of
> > rq->next_balance in a rb-tree
> 
> Given that this list will need to be global (and not per-cpu) and it will need 
> to be updated reqularly (even when cpus are busy and as they update their 
> rq->next_balance), that will probably not fly!

On third thoughts, this list needs to be updated only in idle cpu
context (idle cpus going tickless will be inserted in the list (indexed at 
rq->next_balance and cpu exiting idle will need to be removed). So the global 
list may not hurt so much ..will see how that comes up in code.

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