unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <codonell@redhat.com>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
	 nd@arm.com,  GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Reserve static TLS for dynamically loaded initial-exec TLS only [BZ #25051]
Date: Fri, 21 Feb 2020 13:58:25 +0100	[thread overview]
Message-ID: <87d0a8hzbi.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <043f4682-d009-0365-9bdc-f9bd402683b5@redhat.com> (Carlos O'Donell's message of "Thu, 20 Feb 2020 10:05:06 -0500")

* Carlos O'Donell:

> On 2/17/20 11:01 AM, Florian Weimer wrote:
>> * Carlos O'Donell:
>> 
>>> Let me take a stab at this:
>>>
>>> (1) File a bug to indicate all libraries must stop using
>>>     TLS IE to fix dlmopen issues with TLS IE.
>> 
>> Do you mean glibc components, or do you view this as a distribution-wide
>> change?
>
> All glibc libraries should stop using TLS IE and we should file bugs for
> fixing these instances where TLS IE was used to work around startup ordering
> problems.

This has performance implications, in particular for malloc.
I'll try to get some numbers.

Thanks,
Florian


  reply	other threads:[~2020-02-21 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 11:54 [PATCH] Reserve static TLS for dynamically loaded initial-exec TLS only [BZ #25051] Szabolcs Nagy
2020-01-07 12:09 ` Florian Weimer
2020-01-07 12:50   ` Szabolcs Nagy
2020-02-13 16:38     ` Szabolcs Nagy
2020-02-13 18:07       ` Carlos O'Donell
2020-02-17 16:01         ` Florian Weimer
2020-02-20 15:05           ` Carlos O'Donell
2020-02-21 12:58             ` Florian Weimer [this message]
2020-02-27 16:21               ` Szabolcs Nagy
2020-02-27 16:31                 ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0a8hzbi.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=codonell@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=szabolcs.nagy@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).