[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210514174458.GB19576@hoboy.vegasvil.org>
Date: Fri, 14 May 2021 10:44:58 -0700
From: Richard Cochran <richardcochran@...il.com>
To: "Y.b. Lu" <yangbo.lu@....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
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.
> 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.
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