This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Add GLIBC_PTHREAD_ELISION_ENABLE tunable
- From: Roland McGrath <roland at hack dot frob dot com>
- To: munroesj at linux dot vnet dot ibm dot com
- Cc: "Paul E. Murphy" <murphyp at linux dot vnet dot ibm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, "Carlos O'Donell" <carlos at redhat dot com>, Steve Munroe <sjmunroe at us dot ibm dot com>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, stli at linux dot vnet dot ibm dot com, Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, Siddhesh Poyarekar <siddhesh at redhat dot com>, vapier at gentoo dot org
- Date: Thu, 17 Sep 2015 11:19:45 -0700 (PDT)
- Subject: Re: [PATCH] Add GLIBC_PTHREAD_ELISION_ENABLE tunable
- Authentication-results: sourceware.org; auth=none
- References: <55F33220 dot 8050105 at linux dot vnet dot ibm dot com> <20150917043712 dot GA6834 at vapier dot lan> <55FACCF4 dot 1050200 at linux dot vnet dot ibm dot com> <20150917175102 dot 39DD32C3B22 at topped-with-meat dot com> <1442513371 dot 10636 dot 2 dot camel at oc7878010663>
> On Thu, 2015-09-17 at 10:51 -0700, Roland McGrath wrote:
> > There should be no explicit code using new environment variables at all.
> > It should all go through the tunables framework so policy and knowledge
> > about use of environment variables is centralized.
> >
> So how do we actually move that along?
>
> Because it is not moving?
What we agreed at the Cauldron was that the first step should be the
internal API for tunables, with a stub implementation that does not
implement new external mechanisms like new environment variables. With
that in place, we can experiment concretely with specific "back ends" and
start achieving consensus. But people seem to be be doing things in a
different order than what was agreed.