This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Put CPU-related tunables into a unique namespace?
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 11 Jul 2018 15:20:12 -0400
- Subject: Put CPU-related tunables into a unique namespace?
Should we use an arch namespace for CPU-related tunables?
e.g.
glibc.tune.x86.*
glibc.tune.aarch64.*
glibc.tune.power.*
We currently have:
glibc.tune.
.hwcaps
.cached_memopt
.cpu
Which all look like they are "generic", but .hwcaps is
x86 only, .cached_memopt is ppc only, and .cpu is aarch64
only.
At least HJ has been using x86_* as a name prefix. Which
is another alternative.
My preference is a unique namespace to let the machine
maintainers add whatever they want in that namespace without
collisions between CPUs.
Thoughts?
--
Cheers,
Carlos.