Re: [PATCH 3/4] Enhance --enable-tunables to select tunables frontend at build time

[Florian Weimer <fweimer at redhat dot com>]

On 11/16/2016 09:35 AM, Siddhesh Poyarekar wrote:
> At the GNU Tools Cauldron 2016, the state of the current tunables
> patchset was considered OK with the addition of a way to select the
> frontend to be used for the tunables.  That is, to avoid being locked
> in to one type of frontend initially, it should be possible to build
> tunables with a different frontend with something as simple as a
> configure switch.
>
> To that effect, this patch enhances the --enable-tunables option to
> accept more values than just 'yes' or 'no'.  The current frontend (and
> default when enable-tunables is 'yes') is called 'valstring', to
> select the frontend where a single environment variable is set to a
> colon-separated value string.  More such frontends can be added in
> future.

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.

Thanks,
Florian