| 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, 3 Apr 2007 19:27:36 +0200 From: Andi Kleen <andi@...stfloor.org> To: Ulrich Drepper <drepper@...hat.com> Cc: Andi Kleen <andi@...stfloor.org>, Linux Kernel <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: getting processor numbers On Tue, Apr 03, 2007 at 10:17:15AM -0700, Ulrich Drepper wrote: > Andi Kleen wrote: > > There was a proposal some time ago to put that into the ELF aux vector > > Unfortunately there was disagreement on what information to put > > there exactly (full topology, only limited numbers etc.) > > Topology, yes, I'm likely in favor of it. What topology and what use case? > Processor number: no. Unless you want to rip out hotpluging. I'm Topology is dependent on the number of CPUs. Hot plugging is a completely orthogonal problem. Even your original proposal wouldn't address it. Mine doesn't neither, because i suspect most programs won't care. If it's addressed it could work on top of it. The aux vector to get the information quickly at program startup and later updates can get it from /sys. If some program starts caring we would need to implement some notification mechanism (that would be possible), but it might be hard to fit into glibc because you don't have a event loop. -Andi - 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