From: Paul Eggert <eggert@cs.ucla.edu>
To: Carlos O'Donell <codonell@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Fix multiple minor tzset glitches [BZ #24004]
Date: Thu, 11 Apr 2019 10:51:30 -0700 [thread overview]
Message-ID: <a826dec6-6241-3b5f-3c96-b4353f85e1f7@cs.ucla.edu> (raw)
In-Reply-To: <1be6d504-94b4-475d-9b36-43381a4d07f8@redhat.com>
On 4/10/19 6:18 AM, Carlos O'Donell wrote:
> I think there *have* to be ways in which this data can be dynamically
> updated without a huge performance penalty.
What ways are those, though? It's not like the penalty is zero.
One possible compromise would be for localtime to poll, and for
localtime_r to not poll (you must call tzset to poll), and tell people
"if you want performance, use localtime_r". That might hit a sweet spot
of doing polling for naive programs where performance matters, and
giving higher performance for applications that care about timestamp
performance.
next prev parent reply other threads:[~2019-04-11 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:37 [PATCH] Fix multiple minor tzset glitches [BZ #24004] Paul Eggert
2019-02-18 9:37 ` Florian Weimer
2019-02-20 19:29 ` Paul Eggert
2019-03-13 14:52 ` Florian Weimer
2019-03-13 17:02 ` Paul Eggert
2019-03-14 14:10 ` Florian Weimer
2019-03-14 16:47 ` Paul Eggert
2019-03-14 18:24 ` Adhemerval Zanella
2019-03-14 18:48 ` Florian Weimer
2019-03-15 13:12 ` Yann Droneaud
2019-03-15 15:05 ` Florian Weimer
2019-03-15 16:01 ` Yann Droneaud
2019-04-10 11:57 ` Florian Weimer
2019-04-10 13:18 ` Carlos O'Donell
2019-04-11 17:51 ` Paul Eggert [this message]
2019-04-12 17:07 ` Carlos O'Donell
2019-04-12 18:41 ` Paul Eggert
2019-04-12 18:57 ` Carlos O'Donell
2019-04-12 19:26 ` 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=a826dec6-6241-3b5f-3c96-b4353f85e1f7@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=codonell@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).