From: Sebastien Laveze <sebastien.laveze@oss.nxp.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yangbo.lu@nxp.com, yannick.vignon@oss.nxp.com,
rui.sousa@oss.nxp.com
Subject: Re: [PATCH net-next] ptp: add vclock timestamp conversion IOCTL
Date: Fri, 08 Oct 2021 09:13:58 +0200 [thread overview]
Message-ID: <768227b1f347cb1573efb1b5f6c642e2654666ba.camel@oss.nxp.com> (raw)
In-Reply-To: <20211007201927.GA9326@hoboy.vegasvil.org>
On Thu, 2021-10-07 at 13:19 -0700, Richard Cochran wrote:
> On Thu, Oct 07, 2021 at 03:31:43PM +0200, Sebastien Laveze wrote:
> > For example:
> > Let's take a worst case, the PHC is adjusted every 10 ms, vclock every
> > 1 sec with 1 ppm error.
>
> You can't justify adjusting the HW clock and the vclocks
> asynchronously with a single, isolated example.
This was a single worst case example, many asynchronous PHC adjustments
impacting vclocks.
> If two independent processes are both adjusting a clock concurrently,
> asynchronously, and at different control rates, the result will be
> chaos.
This is especially what we want to prove feasible and we think it's
posssible with the following conditions:
-limited frequency adjustments
-offset adjustment in software
> It does not matter that it *might* work for some random setup of
> yours.
>
> The kernel has to function correctly in general, not just in some
> special circumstances.
Of course, so what tests and measurements can we bring on the table to
convince you that it doesn't lead to chaos ?
Thanks,
Sebastien
next prev parent reply other threads:[~2021-10-08 7:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 9:32 [PATCH net-next] ptp: add vclock timestamp conversion IOCTL Sebastien Laveze
2021-09-27 14:59 ` Richard Cochran
2021-09-27 16:00 ` Sebastien Laveze
2021-09-27 20:23 ` Richard Cochran
2021-09-28 11:50 ` Sebastien Laveze
2021-09-28 13:31 ` Richard Cochran
2021-09-29 15:00 ` Sebastien Laveze
2021-09-30 14:35 ` Richard Cochran
2021-10-07 13:31 ` Sebastien Laveze
2021-10-07 20:19 ` Richard Cochran
2021-10-08 7:13 ` Sebastien Laveze [this message]
2021-10-09 18:24 ` Richard Cochran
2021-10-09 18:25 ` Richard Cochran
2021-10-11 12:58 ` Richard Cochran
2021-10-12 16:14 ` Richard Cochran
2021-10-13 9:56 ` Sebastien Laveze
2021-10-13 13:10 ` Richard Cochran
2021-10-13 13:28 ` Sebastien Laveze
2021-10-13 17:54 ` Richard Cochran
2021-10-14 13:27 ` Sebastien Laveze
2021-09-27 18:28 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=768227b1f347cb1573efb1b5f6c642e2654666ba.camel@oss.nxp.com \
--to=sebastien.laveze@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=rui.sousa@oss.nxp.com \
--cc=yangbo.lu@nxp.com \
--cc=yannick.vignon@oss.nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).