This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/9] Add vectorized getenv for glibc use
- From: Andi Kleen <ak at linux dot intel dot com>
- To: Rich Felker <dalias at aerifal dot cx>
- Cc: Carlos O'Donell <carlos at redhat dot com>, Andi Kleen <andi at firstfloor dot org>, libc-alpha at sourceware dot org
- Date: Tue, 14 May 2013 14:00:06 -0700
- Subject: Re: [PATCH 1/9] Add vectorized getenv for glibc use
- References: <1367537252-30831-1-git-send-email-andi at firstfloor dot org> <1367537252-30831-2-git-send-email-andi at firstfloor dot org> <20130503001819 dot GP20323 at brightrain dot aerifal dot cx> <5191E1AF dot 3010302 at redhat dot com> <20130514141001 dot GT20323 at brightrain dot aerifal dot cx>
> >
> > 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