On Tuesday 27 December 2016 05:14 PM, Florian Weimer wrote:
I'm not sure if this patch makes sense at this point because without
alternative frontends, it's impossible to tell if the current
initialization sequence is sufficient.
For example, if we want to load a tunable configuration with very low
cost, we could use ldconfig to pre-parse a configuration file and put it
into /etc/ld.so.cache. But we won't know if the current approach works
until this is actually implemented.
The option --enable-tunables=... doesn't actually do anything beyond
explicitly naming the current tunables frontend implementation. To
write a different frontend, one would not only have to add a new value
to the --enable-tunables=... option but also tweak the current
initialization sequence to suit its frontend without hurting existing
frontends.