From: Godmar Back <godmar@gmail.com>
To: William Tambe <tambewilliam@gmail.com>
Cc: William Tambe via Libc-help <libc-help@sourceware.org>
Subject: Re: Can TLS be implemented switching from MAP_SHARED to MAP_PRIVATE a page reserved for TLS variables ??
Date: Mon, 6 Apr 2020 20:01:20 -0400 [thread overview]
Message-ID: <CAB4+JY+6U7v9Y54jXQP3sE2ymOLB=82z8sVTLZs_6Hivt0m52g@mail.gmail.com> (raw)
In-Reply-To: <CAF8i9mPe0-fMFqrY_F05Gz-Ruyp-ftuHhOnWhShfhAc8EGZJQw@mail.gmail.com>
On Mon, Apr 6, 2020 at 7:57 PM William Tambe via Libc-help
<libc-help@sourceware.org> wrote:
>
> Can TLS be implemented switching from MAP_SHARED to MAP_PRIVATE a page
> reserved for TLS variables ?
>
> Switching such a page from MAP_SHARED to MAP_PRIVATE would effectively
> make it local to that thread.
You're confusing threads and processes.
MAP_PRIVATE means a process-private mapping, not a thread-private mapping.
next prev parent reply other threads:[~2020-04-07 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 23:57 William Tambe
2020-04-07 0:01 ` Godmar Back [this message]
2020-04-07 9:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB4+JY+6U7v9Y54jXQP3sE2ymOLB=82z8sVTLZs_6Hivt0m52g@mail.gmail.com' \
--to=godmar@gmail.com \
--cc=libc-help@sourceware.org \
--cc=tambewilliam@gmail.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).