| 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
| ||
|
Date: Tue, 5 Feb 2013 20:04:48 -0600 From: Nathan Zimmer <nzimmer@....com> To: viresh.kumar@...aro.org, rjw@...k.pl Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, cpufreq@...r.kernel.org, Nathan Zimmer <nzimmer@....com> Subject: [PATCH v2 linux-next 0/2] cpufreq: cpufreq_driver_lock is hot on large systems I am noticing the cpufreq_driver_lock is quite hot. On an idle 512 system perf shows me most of the system time is spent on this lock. This is quite significant as top shows 5% of time in system time. My solution was to first convert the lock to a rwlock and then to the rcu. v2: Rebase to linux-next Nathan Zimmer (2): cpufreq: Convert the cpufreq_driver_lock to a rwlock cpufreq: Convert the cpufreq_driver_lock to use the rcu drivers/cpufreq/cpufreq.c | 150 +++++++++++++++++++++++++--------------------- 1 file changed, 83 insertions(+), 67 deletions(-) -- 1.8.0.1 -- 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/
Powered by blists - more mailing lists