[PATCH 1/9] Add vectorized getenv for glibc use

[Andi Kleen]

> > 
> > That depends on your view of the defined semantics for the new GLIBC_*
> > environment variables.
> > 
> > I for one would like to say that they are read at program startup and
> > never re-read. It makes the most sense for performance and make for a
> > simple and easy to understand runtime behaviour.
> > 
> > Does that make sense?
> 
> Yes, I agree it's probably better behavior. But I thought the patch
> was also changing (to use caching) the treatment of several
> preexisting glibc config variables, in which case it is changing the
> behavior, and if so this should be noted.

Existing variables are not cached with my patch.
Only the new GLIBC_* variables.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only