From: Richard Cochran <richardcochran@gmail.com>
To: Sebastien Laveze <sebastien.laveze@oss.nxp.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: Mon, 27 Sep 2021 07:59:16 -0700 [thread overview]
Message-ID: <20210927145916.GA9549@hoboy.vegasvil.org> (raw)
In-Reply-To: <20210927093250.202131-1-sebastien.laveze@oss.nxp.com>
On Mon, Sep 27, 2021 at 11:32:50AM +0200, Sebastien Laveze wrote:
> Add an IOCTL to perform per-timestamp conversion, as an extension of the
> ptp virtual framework introduced in commit 5d43f951b1ac ("ptp: add ptp
> virtual clock driver framework").
I'm not wild about having yet another ioctl for functionality that
already exists.
> This binding works well if the application requires all timestamps in the
> same domain but is not convenient when multiple domains need to be
> supported using a single socket.
Opening multiple sockets is not rocket science.
> Typically, IEEE 802.1AS-2020 can be implemented using a single socket,
> the CMLDS layer using raw PHC timestamps and the domain specific
> timestamps converted in the appropriate gPTP domain using this IOCTL.
You say "typically", but how many applications actually do this? I
can't think of any at all.
Thanks,
Richard
next prev parent reply other threads:[~2021-09-27 14:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 9:32 Sebastien Laveze
2021-09-27 14:59 ` Richard Cochran [this message]
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
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=20210927145916.GA9549@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rui.sousa@oss.nxp.com \
--cc=sebastien.laveze@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
all inboxes | Powered by JetHome®