From: Richard Cochran <richardcochran@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: gerhard@engleder-embedded.com, davem@davemloft.net,
kuba@kernel.org, mlichvar@redhat.com, netdev@vger.kernel.org,
vinicius.gomes@intel.com, yangbo.lu@nxp.com
Subject: Re: [RFC PATCH net-next 0/6] ptp: Support hardware clocks with additional free running time
Date: Mon, 7 Mar 2022 06:05:31 -0800 [thread overview]
Message-ID: <20220307140531.GA29247@hoboy.vegasvil.org> (raw)
In-Reply-To: <20220307120751.3484125-1-michael@walle.cc>
On Mon, Mar 07, 2022 at 01:07:51PM +0100, Michael Walle wrote:
> Richard Cochran wrote:
> > You are adding eight bytes per frame for what is arguably an extreme
> > niche case.
>
> I don't think it is a niche case, btw. I was always wondering why
> NXP introduced the vclock thingy. And apparently it is for
> 802.1AS-rev, but one use case for that is 802.1Qbv and there you'll
> need a (synchronized) hardware clock to control the gates. So while
> we can have multiple time domain support with the vclock, we cannot
> use Qbv with them. That was something I have always wondered about.
> Or.. maybe I'm missing something here.
Niche is relative.
Believe it or not, the overwhelmingly great majority of people using
Linux have no interest in TSN.
Thanks,
Richard
next prev parent reply other threads:[~2022-03-07 14:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 8:56 [RFC PATCH net-next 0/6] ptp: Support hardware clocks with additional free running time Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 1/6] bpf: Access hwtstamp field of hwtstamps directly Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 2/6] ptp: Initialize skb_shared_hwtstamps Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 3/6] ptp: Add free running time support Gerhard Engleder
2022-03-06 16:36 ` Richard Cochran
2022-03-06 8:56 ` [RFC PATCH net-next 4/6] ptp: Support time stamps based on free running time Gerhard Engleder
2022-03-06 16:42 ` Richard Cochran
2022-03-06 8:56 ` [RFC PATCH net-next 5/6] ptp: Allow vclocks without free running physical clock Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 6/6] tsnep: Add free running time support Gerhard Engleder
2022-03-06 16:49 ` [RFC PATCH net-next 0/6] ptp: Support hardware clocks with additional free running time Richard Cochran
2022-03-06 16:53 ` Richard Cochran
2022-03-06 17:05 ` Richard Cochran
2022-03-06 18:38 ` Gerhard Engleder
2022-03-06 21:50 ` Richard Cochran
2022-03-07 14:34 ` Richard Cochran
2022-03-07 17:54 ` Gerhard Engleder
2022-03-07 21:30 ` Richard Cochran
2022-03-08 0:55 ` Richard Cochran
2022-03-08 19:49 ` Gerhard Engleder
2022-03-08 20:52 ` Richard Cochran
2022-03-08 0:57 ` Richard Cochran
2022-03-07 12:07 ` Michael Walle
2022-03-07 14:05 ` Richard Cochran [this message]
2022-03-07 14:23 ` Miroslav Lichvar
2022-03-07 14:37 ` Richard Cochran
2022-03-08 20:55 ` Richard Cochran
2022-03-07 16:01 ` Gerhard Engleder
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=20220307140531.GA29247@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=gerhard@engleder-embedded.com \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=yangbo.lu@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).