| 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: Mon, 18 Jul 2011 13:44:50 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Gleb Natapov <gleb@...hat.com> Cc: linux-arch@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, "Paul E. McKenney" <paulmck@...ibm.com> Subject: Re: current_thread_info() vs task_thread_info(current) On Mon, 2011-07-18 at 14:36 +0300, Gleb Natapov wrote: > Why not use per cpu kernel_stack variable on all arches as x86_64 does? > How big the advantage of using stack pointer to find current thread info is? One less load I imagine. -- 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