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 for Android: free password hash cracker in your pocket

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

Message-ID: <Y/gCottQVlJTKUlg@hoboy.vegasvil.org>
Date:   Thu, 23 Feb 2023 16:19:46 -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 12:56:34PM -0800, Matt Corallo wrote:

> There's two separate questions here - multiple readers receiving the same
> data, and multiple readers receiving data exclusively about one channel.
> 
> I'd imagine the second is (much?) easier to implement, whereas the first is a bunch of complexity.

This second idea would require a new API, so that user could select a
particular channel.

First idea would only change kernel behavior without changing the API.

Thanks,
Richard