public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at deneb dot enyo.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/30200] time sometimes appears to go backwards
Date: Tue, 21 Mar 2023 20:25:35 +0000	[thread overview]
Message-ID: <bug-30200-131-pnQc79Pd5J@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30200-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30200

Florian Weimer <fw at deneb dot enyo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fw at deneb dot enyo.de

--- Comment #17 from Florian Weimer <fw at deneb dot enyo.de> ---
(In reply to Bruno Haible from comment #15)
> (In reply to Adhemerval Zanella from comment #14)
> > Florian explicit say he would revert it
> > on RH distros because of performance implications. 

I think I said, or should have said, that we would have to revert it based on
customer/partner feedback if performance problems are reported (which would
only happen a couple of years down the road).

> If the question cannot be decided due to different distro priorities (for
> some distros, logging speed is super important, while for other distros,
> correctness and interoperability is the focus), then how about changing the
> patch so that it adds a glibc configure option? Such as
> --enable/disable-fast-time or --enable/disable-correct-time?

This won't help you with the gnulib testsuite.

In any case, if you don't like the time-related services the kernel provides, I
think you really should take this up with the kernel developers. We are just
handing down what the kernel provides to us.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-21 20:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 17:21 [Bug time/30200] New: " bruno at clisp dot org
2023-03-05 17:22 ` [Bug time/30200] " bruno at clisp dot org
2023-03-05 17:23 ` bruno at clisp dot org
2023-03-05 17:55 ` girish946 at gmail dot com
2023-03-05 18:28 ` schwab@linux-m68k.org
2023-03-05 18:58 ` schwab@linux-m68k.org
2023-03-05 19:04 ` bruno at clisp dot org
2023-03-06 12:15 ` adhemerval.zanella at linaro dot org
2023-03-06 12:25 ` fweimer at redhat dot com
2023-03-06 12:45 ` bruno at clisp dot org
2023-03-06 13:08 ` adhemerval.zanella at linaro dot org
2023-03-06 13:14 ` fweimer at redhat dot com
2023-03-19 23:43 ` eggert at cs dot ucla.edu
2023-03-21  4:18 ` sam at gentoo dot org
2023-03-21 15:06 ` adhemerval.zanella at linaro dot org
2023-03-21 15:29 ` bruno at clisp dot org
2023-03-21 16:02 ` adhemerval.zanella at linaro dot org
2023-03-21 20:00 ` bruno at clisp dot org
2023-03-21 20:03 ` adhemerval.zanella at linaro dot org
2023-03-21 20:25 ` fw at deneb dot enyo.de [this message]
2023-03-21 20:41 ` adhemerval.zanella at linaro dot org

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=bug-30200-131-pnQc79Pd5J@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).