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, 12 Nov 2013 19:08:44 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Dietmar Eggemann <dietmar.eggemann@....com> Cc: Martin Schwidefsky <schwidefsky@...ibm.com>, Vincent Guittot <vincent.guittot@...aro.org>, linux-kernel <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...nel.org>, Paul Turner <pjt@...gle.com>, Morten Rasmussen <Morten.Rasmussen@....com>, "cmetcalf@...era.com" <cmetcalf@...era.com>, "tony.luck@...el.com" <tony.luck@...el.com>, Alex Shi <alex.shi@...el.com>, Preeti U Murthy <preeti@...ux.vnet.ibm.com>, "linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Paul McKenney <paulmck@...ux.vnet.ibm.com>, Jonathan Corbet <corbet@....net>, Thomas Gleixner <tglx@...utronix.de>, Len Brown <len.brown@...el.com>, Arjan van de Ven <arjan@...ux.intel.com>, Amit Kucheria <amit.kucheria@...aro.org>, Lukasz Majewski <l.majewski@...sung.com>, "james.hogan@...tec.com" <james.hogan@...tec.com>, "heiko.carstens@...ibm.com" <heiko.carstens@...ibm.com> Subject: Re: [RFC][PATCH v5 01/14] sched: add a new arch_sd_local_flags for sched_domain init On Tue, Nov 12, 2013 at 05:43:36PM +0000, Dietmar Eggemann wrote: > This patch removes the sched_domain initializer macros > SD_[SIBLING|MC|BOOK|CPU]_INIT in core.c and in archs and replaces them > with calls to the new function sd_init(). The function sd_init > incorporates the already existing function sd_numa_init(). Your patch retains far too much of the weird behavioural variations we have, nor does it create a proper separation between topology and behaviour. We might indeed have to have a single arch_() function that adds SD_flags, but please restrict the flags it can set -- never allow it to set behavioural flags. Furthermore, I think we want to allow the arch to override the base topology; we've had desire to add per arch level in the past.. eg. add an L2 level for some x86 variants. -- 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