From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Lunn <andrew@lunn.ch>, Simon Dietz <simon.dietz@plantwatch.de>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net,
dietz23838@hs-ansbach.de, edumazet@google.com,
kuniyu@google.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: short description of GeoNetworking
Date: Thu, 23 Jul 2026 14:37:28 +0200 [thread overview]
Message-ID: <127c720f9ceeaac6ec3872bfc7732ab27d968dfc.camel@sipsolutions.net> (raw)
In-Reply-To: <70e14ff7-fa2f-42a9-b880-a6adf5713c10@lunn.ch>
On Thu, 2026-07-23 at 02:30 +0200, Andrew Lunn wrote:
>
>
> Closest to the target. Opposite to how i interpreted it. I still think
> a device in the middle might be better, but that needs a true WiFi
> person to comment on it.
I didn't really want to comment much on this, but I guess you're calling
me out ;-)
I _think_ in 11p there isn't much notion of being able to do rate
adaptation, so it probably doesn't matter (much) from an airtime usage
POV (if the frame makes it through at all). From a robustness POV it
might matter more, but then it also depends how you select which
stations you consider to be reachable at all.
As for the user-space vs. kernel-space split: clearly, only highly
specialised applications are going to be able to use this socket family
at all, not only because it's a special socket family, but also because
they're going to have to figure out where to send a packet?
Or put another way: for each packet, you need to know _where_ (as in
physical location) it's going to go, so you can pick which peer to send
it to, no? Is this really a *per-packet* property? If not, then I don't
think the shape calculations etc. would really need to be in the kernel?
In fact I'm sort of asking myself if - since the applications are so
specialized - it even makes sense to have a socket family for it? Not
sure, lacking the high-level design context I guess.
A bigger issue with this might be that it's clearly a small piece of a
large overall puzzle - Simon, you mentioned a modified driver somewhere
I think (can't find that mention right now), which may be using the OCB
support in the stack, perhaps, but also isn't upstream.
> So looking at it from this perspective, how does the Linux Foundation
> Automotive Grade Linux fit in? Does it have a V2V stack? Is it kernel
> or user space? If they have a full implementation, which is open
> source, but just out of tree, with a range of applications, would it
> be better to spend some time to clean up and merge their code?
And then also related to that - it seems these would be very specialized
applications to start with, how do we get anything useful out of a
socket family without them?
johannes
prev parent reply other threads:[~2026-07-23 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 21:00 [RFC PATCH net-next v0.1 0/1] add GeoNetworking protocol Simon Dietz
2026-07-18 21:00 ` [RFC PATCH net-next v0.1 1/1] net: " Simon Dietz
2026-07-19 17:16 ` Andrew Lunn
2026-07-19 17:28 ` Andrew Lunn
2026-07-19 23:33 ` Andrew Lunn
2026-07-19 16:21 ` [RFC PATCH net-next v0.1 0/1] " Andrew Lunn
2026-07-20 18:36 ` short description of GeoNetworking Simon Dietz
2026-07-20 20:16 ` Andrew Lunn
2026-07-22 21:34 ` Simon Dietz
2026-07-23 0:30 ` Andrew Lunn
2026-07-23 12:37 ` Johannes Berg [this message]
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=127c720f9ceeaac6ec3872bfc7732ab27d968dfc.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dietz23838@hs-ansbach.de \
--cc=edumazet@google.com \
--cc=kuniyu@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.dietz@plantwatch.de \
/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