netdev - RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks

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]

Date:   Wed, 15 Dec 2021 12:14:39 +0000
From:   "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
To:     "Machnikowski, Maciej" <maciej.machnikowski@...el.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Vadim Fedorenko <vfedorenko@...ek.ru>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
        "richardcochran@...il.com" <richardcochran@...il.com>,
        "Byagowi, Ahmad" <abyagowi@...com>,
        "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
        "idosch@...sch.org" <idosch@...sch.org>,
        "mkubecek@...e.cz" <mkubecek@...e.cz>,
        "saeed@...nel.org" <saeed@...nel.org>,
        "michael.chan@...adcom.com" <michael.chan@...adcom.com>,
        "petrm@...dia.com" <petrm@...dia.com>
Subject: RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks

> -----Original Message-----
> From: Machnikowski, Maciej <maciej.machnikowski@...el.com> 
> Sent: poniedziałek, 13 grudnia 2021 09:54
> To: Jakub Kicinski <kuba@...nel.org>
> Cc: netdev@...r.kernel.org; intel-wired-lan@...ts.osuosl.org; Kubalewski, Arkadiusz <arkadiusz.kubalewski@...el.com>; richardcochran@...il.com; Byagowi, Ahmad <abyagowi@...com>; Nguyen, Anthony L <anthony.l.nguyen@...el.com>; davem@...emloft.net; linux-kselftest@...r.kernel.org; idosch@...sch.org; mkubecek@...e.cz; saeed@...nel.org; michael.chan@...adcom.com; petrm@...dia.com; Vadim Fedorenko <vfedorenko@...ek.ru>
> Subject: RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
> 
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@...nel.org>
> > Sent: Friday, December 10, 2021 5:17 PM
> > To: Machnikowski, Maciej <maciej.machnikowski@...el.com>
> > Cc: netdev@...r.kernel.org; intel-wired-lan@...ts.osuosl.org; 
> > Kubalewski, Arkadiusz <arkadiusz.kubalewski@...el.com>; 
> > richardcochran@...il.com; Byagowi, Ahmad <abyagowi@...com>; Nguyen, 
> > Anthony L <anthony.l.nguyen@...el.com>; davem@...emloft.net; linux- 
> > kselftest@...r.kernel.org; idosch@...sch.org; mkubecek@...e.cz; 
> > saeed@...nel.org; michael.chan@...adcom.com; petrm@...dia.com; Vadim 
> > Fedorenko <vfedorenko@...ek.ru>
> > Subject: Re: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
> > 
> > On Fri, 10 Dec 2021 14:45:46 +0100 Maciej Machnikowski wrote:
> > > Synchronous Ethernet networks use a physical layer clock to 
> > > syntonize the frequency across different network elements.
> > >
> > > Basic SyncE node defined in the ITU-T G.8264 consist of an Ethernet 
> > > Equipment Clock (EEC) and have the ability to synchronize to 
> > > reference frequency sources.
> > >
> > > This patch series is a prerequisite for EEC object and adds ability 
> > > to enable recovered clocks in the physical layer of the netdev object.
> > > Recovered clocks can be used as one of the reference signal by the EEC.
> > >
> > > Further work is required to add the DPLL subsystem, link it to the 
> > > netdev object and create API to read the EEC DPLL state.
> > 
> > You missed CCing Vadim. I guess Ccing the right people may be right up 
> > there with naming things as the hardest things in SW development..
> > 
> > Anyway, Vadim - do you have an ETA on the first chunk of the PLL work?
> 
> Sounds about right :) thanks for adding Vadim!
> 

Good day Vadim,

Can we help on the new PLL interfaces?
I can start some works related to that, although would need a guidance
from the expert. 
Where to place it?
What in-kernel interfaces to use?
Any other high level tips that could be useful?
Or if you already started some work, could you please share some
information?