This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v4] Make bindresvport() function to multithread-safe
On Thu, Oct 25, 2012 at 12:31 PM, Roland McGrath <roland@hack.frob.com> wrote:
> I think it is indeed obvious without "collecting data" that bindresvport is
> both not used widely, and not used frequently in programs that use it. Its
> purpose is something that only certain network programs would do, and that
> they would do only at startup (or perhaps connection startup).
Is this statement based on your experience as a developer?
Honestly, I just don't have enough experience to evaluate the usage
of bindresvport. Though I'm willing to accept such experience from Rich
and yourself.
> A local lock satisfies the purposes and does not impose any cost on the
> vast majority of programs that do not use the function. Another solution
> like using TLS that has collateral cost is only ever warranted once it's
> positively demonstrated that the locking approach is too costly in practice.
Just to be clear the "collatoral cost" is only the initial relocation processing
and the .tdata size added to each thread?
Cheers,
Carlos.