netdev - Re: [chrony-dev] Support for Multiple PPS Inputs on single PHC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y/hGIQzT7E48o3Hz@hoboy.vegasvil.org>
Date:   Thu, 23 Feb 2023 21:07:45 -0800
From:   Richard Cochran <richardcochran@...il.com>
To:     Matt Corallo <ntp-lists@...tcorallo.com>
Cc:     Miroslav Lichvar <mlichvar@...hat.com>,
        chrony-dev@...ony.tuxfamily.org,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [chrony-dev] Support for Multiple PPS Inputs on single PHC

On Thu, Feb 23, 2023 at 05:18:06PM -0800, Matt Corallo wrote:

> It sounds like I should go replace the extts queue with a circular buffer,
> have every reader socket store an index in the buffer, and new sockets read
> only futures pulses?

Single circular buffer with multiple heads will be complex.

It might be simpler to allocate one queue per reader.

If there are few readers, cost of allocation and en-queuing won't matter.

Thanks,
Richard