[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB7PR04MB5017A20680D117571A568905F82D9@DB7PR04MB5017.eurprd04.prod.outlook.com>
Date: Mon, 17 May 2021 02:46:05 +0000
From: "Y.b. Lu" <yangbo.lu@....com>
To: Richard Cochran <richardcochran@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
Claudiu Manoil <claudiu.manoil@....com>,
Jakub Kicinski <kuba@...nel.org>
Subject: RE: [net-next 0/6] ptp: support virtual clocks for multiple domains
> -----Original Message-----
> From: Richard Cochran <richardcochran@...il.com>
> Sent: 2021年5月15日 1:45
> To: Y.b. Lu <yangbo.lu@....com>
> Cc: netdev@...r.kernel.org; David S . Miller <davem@...emloft.net>; Claudiu
> Manoil <claudiu.manoil@....com>; Jakub Kicinski <kuba@...nel.org>
> Subject: Re: [net-next 0/6] ptp: support virtual clocks for multiple domains
>
> On Fri, May 14, 2021 at 06:41:28AM +0000, Y.b. Lu wrote:
> > I give up supporting physical clock and the timecounters adjusting at the
> same time, but I may continue to support virtual clock per your suggestion.
>
> Okay, so the physical clock stays free running when virtual clocks are active.
Yes.
>
> > Getting back to your user space idea, I'd like to understand further to see if I
> can make some contribution.
> > Actually I can't think out how to track (there is not timecouner like in kernel)
> in a easy way, and I have some concerns too.
>
> Maybe I was not clear before. You can implement the virtual clocks in the
> kernel. User space will not need to be involved.
>
Thank you very much to make it clear for me.
> It is easy for the kernel to hide the physical clock when virtual clocks are
> created from it.
>
> Thanks,
> Richard
Powered by blists - more mailing lists