From: Richard Cochran <richardcochran@gmail.com>
To: "Stern, Avraham" <avraham.stern@intel.com>
Cc: "Greenman, Gregory" <gregory.greenman@intel.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: pull-request: wireless-next-2023-03-30
Date: Wed, 26 Apr 2023 07:04:30 -0700 [thread overview]
Message-ID: <ZEkvbvIZiUnbK45N@hoboy.vegasvil.org> (raw)
In-Reply-To: <ZEiP3LDTQ86c4HaN@hoboy.vegasvil.org>
On Tue, Apr 25, 2023 at 07:43:40PM -0700, Richard Cochran wrote:
> Your design might touch upon a number of points...
I forgot the most important point, IMO:
How will you handle time distribution across a wireless network?
Consider the following simple case.
GPS Radio ------> Station-A ~~~~~~ AP ~~~~~~ Station-B
1PPS WiFi WiFi
Here Station-A should become the PTP server, and Station-B should
become a PTP client. In 1588, this is accomplished by forming a
spanning tree over the wired network, based on time quality fields
advertised.
AFAICT, the standards provide almost no hint how this is supposed to
work over WiFi. I'd like to know your plans for solving this aspect.
Just exposing FTM to user space doesn't help all.
It gets even better.
Replace that "AP" with "mesh network" and image Station-B moves around...
What happens next?
Thanks,
Richard
next prev parent reply other threads:[~2023-04-26 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 20:56 pull-request: wireless-next-2023-03-30 Johannes Berg
2023-03-31 7:06 ` Jakub Kicinski
2023-04-03 22:45 ` Richard Cochran
2023-04-13 3:33 ` Richard Cochran
2023-04-18 13:35 ` Greenman, Gregory
2023-04-20 3:43 ` Richard Cochran
2023-04-23 13:33 ` Stern, Avraham
2023-04-24 22:04 ` Richard Cochran
2023-04-25 1:29 ` Richard Cochran
2023-04-25 7:03 ` Stern, Avraham
2023-04-26 2:43 ` Richard Cochran
2023-04-26 14:04 ` Richard Cochran [this message]
2023-05-07 16:32 ` Stern, Avraham
2023-03-31 7:10 ` patchwork-bot+netdevbpf
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=ZEkvbvIZiUnbK45N@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=avraham.stern@intel.com \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).