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: Fri, 29 Nov 2013 18:36:57 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Eliezer Tamir <eliezer.tamir@...ux.intel.com> Cc: John Stultz <john.stultz@...aro.org>, Thomas Gleixner <tglx@...utronix.de>, Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Andy Lutomirski <luto@...capital.net>, linux-kernel@...r.kernel.org, Tony Luck <tony.luck@...il.com>, hpa@...or.com, Peter Zijlstra <peterz@...radead.org> Subject: [RFC][PATCH 0/7] sched: Optimize sched_clock bits Hi all, This series is supposed to optimize the kernel/sched/clock.c and x86 sched_clock() implementations. So far its only been boot tested. So no clue if it really makes the thing faster, but it does remove the need to disable IRQs. I'm hoping Eliezer will test this with his benchmark where he could measure a performance regression between using sched_clock() and local_clock(). It looks like ia64, the only other CONFIG_HAVE_UNSTABLE_SCHED_CLOCK user, already matches the new expectations -- mostly not requiring IRQs disabled for calling sched_clock(). -- 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