From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>
Subject: Re: [PATCH v4 2/5] batman-adv: tvlv: prepare for tvlv enabled multicast packet type
Date: Fri, 06 Jan 2023 18:54:08 +0100 [thread overview]
Message-ID: <3853553.NG923GbCHz@sven-l14> (raw)
In-Reply-To: <20221227193409.13461-3-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
On Tuesday, 27 December 2022 20:34:06 CET Linus Lüssing wrote:
> Prepare TVLV infrastructure for more packet types, in particular the
> upcoming batman-adv multicast packet type.
>
> For that swap the OGM vs. unicast-tvlv packet boolean indicator to an
> explicit unsigned integer packet type variable. And provide the skb
> to a call to batadv_tvlv_containers_process(), as later the multicast
> packet's TVLV handler will need to have access not only to the TVLV but
> the full skb for forwarding. Forwarding will be invoked from the
> multicast packet's TVLVs' contents later.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
> include/uapi/linux/batadv_packet.h | 2 +
> net/batman-adv/bat_v_ogm.c | 4 +-
> net/batman-adv/distributed-arp-table.c | 2 +-
> net/batman-adv/gateway_common.c | 2 +-
> net/batman-adv/multicast.c | 2 +-
> net/batman-adv/network-coding.c | 2 +-
> net/batman-adv/routing.c | 7 ++-
> net/batman-adv/translation-table.c | 4 +-
> net/batman-adv/tvlv.c | 71 ++++++++++++++++++--------
> net/batman-adv/tvlv.h | 9 ++--
> net/batman-adv/types.h | 6 +++
> 11 files changed, 74 insertions(+), 37 deletions(-)
I am rather unhappy that the TVLV handlers parts are not static, constant,
global objects which are just presented to batadv_tvlv_handler_register. The
batadv_tvlv_containers_process parameters start to become a mess. Anyway, this
has not really anything to do with your patch.
Acked-by: Sven Eckelmann <sven@narfation.org>
Just wondering if it is a good idea to use the network/transport header
offsets/pointers like this.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-06 17:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 19:34 [PATCH v4 0/5] Implementation of a Stateless Multicast Packet Type Linus Lüssing
2022-12-27 19:34 ` [PATCH v4 1/5] batman-adv: mcast: remove now redundant single ucast forwarding Linus Lüssing
2023-01-06 17:21 ` Sven Eckelmann
2022-12-27 19:34 ` [PATCH v4 2/5] batman-adv: tvlv: prepare for tvlv enabled multicast packet type Linus Lüssing
2023-01-06 17:54 ` Sven Eckelmann [this message]
2022-12-27 19:34 ` [PATCH v4 3/5] batman-adv: mcast: implement multicast packet reception and forwarding Linus Lüssing
2023-01-15 17:56 ` Sven Eckelmann
2023-01-16 18:31 ` Linus Lüssing
2023-01-19 12:47 ` Simon Wunderlich
2023-01-21 13:15 ` Linus Lüssing
2022-12-27 19:34 ` [PATCH v4 4/5] batman-adv: mcast: implement multicast packet generation Linus Lüssing
2023-01-18 21:15 ` Sven Eckelmann
2022-12-27 19:34 ` [PATCH v4 5/5] batman-adv: mcast: shrink tracker packet after scrubbing Linus Lüssing
2023-01-18 21:29 ` Sven Eckelmann
2023-01-27 9:26 ` [PATCH v4 0/5] Implementation of a Stateless Multicast Packet Type Sven Eckelmann
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=3853553.NG923GbCHz@sven-l14 \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
/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