From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E18C738515CC; Tue, 21 Mar 2023 20:41:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E18C738515CC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1679431266;
	bh=QF/E+wiIGhS/MtxY4hXDF7vHvn7y0pEWBD99Kk+S8+Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=kdug+Bd5FVpEo4KsXUBczZWuybv+mSn4UgaMo0/qvLtRcrjySOby0cEp02pzqW8Jq
	 ME7zyGxneh+X66ZnA0oXtyRwMwHIAipzOe0Y8lU3iEA/ncUWKIfhAFIyZ64xc2HHpW
	 lWyJbDFO4xLQM3gkOWbnICsg/MPIz1O63E3xOP0s=
From: "adhemerval.zanella at linaro dot org"
 <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:41:06 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: time
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adhemerval.zanella at linaro dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30200-131-dnXK55nVNS@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30200-131@http.sourceware.org/bugzilla/>
References: <bug-30200-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

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

--- Comment #18 from Adhemerval Zanella <adhemerval.zanella at linaro dot o=
rg> ---
(In reply to Florian Weimer from comment #17)
> (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.=20
>=20
> 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).

And it basically would require all the gnulib hackery to fix this issue aga=
in
if this is ever done.  It also means that if gnulib is used users will need=
 to
add even extra hackery to get this time performance difference.

>=20
> > If the question cannot be decided due to different distro priorities (f=
or
> > 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?
>=20
> This won't help you with the gnulib testsuite.
>=20
> 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 develope=
rs.
> We are just handing down what the kernel provides to us.

I don't think we should follow kernel blindly here, especially if this does
generate potential issues as Paul has summarized.  And users always have the
option to use clock_gettime (CLOCK_REALTIME_COARSE).

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