[patch v4 0/4] System-wide tunables

[DJ Delorie]

Yury Khrustalev <yury.khrustalev@arm.com> writes:
>> >    - should the cache be reloadable over the life of a running program
>
> Depends on when each tunable is used (has effect).

We only load the tunables portion of the cache at startup.  The cache
reload only really affect dlopen.

>> >    - how much pre-processing, pre-warning, etc should ldconfig do
>
> Probably do robust error reporting with LD_DEBUG=tunables and otherwise
> do one of the 2 things: fall-back to default or abort (depending on the
> property of each tunable).

I think it should always warn, but a setting to force error/abort sounds
useful.

>> > For the first, I argued for a separate file to keep from interfering
>> > with sysadmins or scripts managing ld.so.conf, but process it with
>> > ldconfig so that sysadmins or scripts that don't know about tunables
>> > will at least do the right thing.  The counter argument is that having a
>> > second set of file parsing code is more complexity and a source of bugs,
>> > but the code is relatively short and copied from existing code.
>
> Why can't we re-use the existing code to avoid duplication?

The amount of change needed to make that code flexible is about the same
as just copying the code.  It's not really that much code to do the
include handling, since a lot of it *is* shared.