Date: Thu, 03 Dec 2020 22:13:34 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Ian Lepore <ian@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: struct timex and Linux adjtimex() Message-ID: <25989.1607033614@critter.freebsd.dk> In-Reply-To: <202012032203.0B3M3VJx004269@slippy.cwsent.com> References: <202012030523.0B35NsG7003810@slippy.cwsent.com> <4086.1606982335@critter.freebsd.dk> <5e0db735b29f1ece02521871b2cd392c3467101d.camel@freebsd.org> <25487.1607029223@critter.freebsd.dk> <202012032203.0B3M3VJx004269@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- Cy Schubert writes: > I will go back > with my initial proposal of a timespec add/subtract syscall takes a > timespec as input increments or decrements the clock by the timespec and > returns a timespec with the time. I would be tempted by the clock_settime(2) "clock_id" argument. The functionality required has a LOT more commonality with clock_settime(2) than with ntp_adjtime(2), and absconding with a couple of the top bits of clock_id for "CLOCK_ADD_ADJUSTMENT" and "CLOCK_SUB_ADJUSTMENT" would be be a pretty clean solution. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25989.1607033614>