From: Vladimir Oltean <olteanv@gmail.com>
To: Mattias Forsblad <mattias.forsblad@gmail.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v8 3/6] net: dsa: Introduce dsa tagger data operation.
Date: Sun, 11 Sep 2022 16:46:24 +0300 [thread overview]
Message-ID: <20220911134624.24a5pjlw77z6b7f3@skbuf> (raw)
In-Reply-To: <20220909085138.3539952-4-mattias.forsblad@gmail.com> <20220909085138.3539952-4-mattias.forsblad@gmail.com>
A proper prefix for this patch would be "net: dsa: tag_dsa: ", since
"net: dsa:" refers to the whole subsystem.
On Fri, Sep 09, 2022 at 10:51:35AM +0200, Mattias Forsblad wrote:
> Support connecting dsa tagger for frame2reg decoding
> with it's associated hookup functions.
s/it's/its/
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
> Signed-off-by: Mattias Forsblad <mattias.forsblad@gmail.com>
> ---
> include/net/dsa.h | 5 +++++
> net/dsa/tag_dsa.c | 32 +++++++++++++++++++++++++++++---
> 2 files changed, 34 insertions(+), 3 deletions(-)
>
> diff --git a/include/net/dsa.h b/include/net/dsa.h
> index 0e8a7ef17490..8510267d6188 100644
> --- a/include/net/dsa.h
> +++ b/include/net/dsa.h
> @@ -130,6 +130,11 @@ struct dsa_lag {
> refcount_t refcount;
> };
>
> +struct dsa_tagger_data {
> + void (*decode_frame2reg)(struct net_device *netdev,
> + struct sk_buff *skb);
> +};
> +
You probably mean to put this in include/linux/dsa/mv88e6xxx.h. Despite
the common naming, there is a big difference between DSA the framework
and DSA the Marvell implementation.
> struct dsa_switch_tree {
> struct list_head list;
>
> diff --git a/net/dsa/tag_dsa.c b/net/dsa/tag_dsa.c
> index e4b6e3f2a3db..3dd1dcddaf05 100644
> --- a/net/dsa/tag_dsa.c
> +++ b/net/dsa/tag_dsa.c
> @@ -198,7 +198,10 @@ static struct sk_buff *dsa_xmit_ll(struct sk_buff *skb, struct net_device *dev,
> static struct sk_buff *dsa_rcv_ll(struct sk_buff *skb, struct net_device *dev,
> u8 extra)
> {
> + struct dsa_tagger_data *tagger_data;
> + struct dsa_port *dp = dev->dsa_ptr;
> bool trap = false, trunk = false;
> + struct dsa_switch *ds = dp->ds;
> int source_device, source_port;
> enum dsa_code code;
> enum dsa_cmd cmd;
> @@ -218,9 +221,9 @@ static struct sk_buff *dsa_rcv_ll(struct sk_buff *skb, struct net_device *dev,
>
> switch (code) {
> case DSA_CODE_FRAME2REG:
> - /* Remote management is not implemented yet,
> - * drop.
> - */
> + tagger_data = ds->tagger_data;
You allocate one ds->tagger_data structure for each switch in the tree,
but you always use the tagger_data of the upstream-most "ds", the one
associated with the cpu_dp behind master->dsa_ptr.
How about minimally parsing the skb within the tagger, to figure out the
proper destination switch, and pass to tagger_data->decode_frame2reg()
the actual correct ds, plus a pointer to the skb so you can take a
reference on it?
> + if (likely(tagger_data->decode_frame2reg))
> + tagger_data->decode_frame2reg(dev, skb);
> return NULL;
> case DSA_CODE_ARP_MIRROR:
> case DSA_CODE_POLICY_MIRROR:
> @@ -323,6 +326,25 @@ static struct sk_buff *dsa_rcv_ll(struct sk_buff *skb, struct net_device *dev,
> return skb;
> }
>
> +static int dsa_tag_connect(struct dsa_switch *ds)
> +{
> + struct dsa_tagger_data *tagger_data;
> +
> + tagger_data = kzalloc(sizeof(*tagger_data), GFP_KERNEL);
> + if (!tagger_data)
> + return -ENOMEM;
> +
> + ds->tagger_data = tagger_data;
> +
> + return 0;
> +}
> +
> +static void dsa_tag_disconnect(struct dsa_switch *ds)
> +{
> + kfree(ds->tagger_data);
> + ds->tagger_data = NULL;
> +}
> +
> #if IS_ENABLED(CONFIG_NET_DSA_TAG_DSA)
>
> static struct sk_buff *dsa_xmit(struct sk_buff *skb, struct net_device *dev)
> @@ -343,6 +365,8 @@ static const struct dsa_device_ops dsa_netdev_ops = {
> .proto = DSA_TAG_PROTO_DSA,
> .xmit = dsa_xmit,
> .rcv = dsa_rcv,
> + .connect = dsa_tag_connect,
> + .disconnect = dsa_tag_disconnect,
> .needed_headroom = DSA_HLEN,
> };
>
> @@ -385,6 +409,8 @@ static const struct dsa_device_ops edsa_netdev_ops = {
> .proto = DSA_TAG_PROTO_EDSA,
> .xmit = edsa_xmit,
> .rcv = edsa_rcv,
> + .connect = dsa_tag_connect,
> + .disconnect = dsa_tag_disconnect,
> .needed_headroom = EDSA_HLEN,
> };
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-09-11 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 8:51 [PATCH net-next v8 0/6] net: dsa: qca8k, mv88e6xxx: rmon: Add RMU support Mattias Forsblad
2022-09-09 8:51 ` [PATCH net-next v8 1/6] net: dsa: mv88e6xxx: Add RMU enable for select switches Mattias Forsblad
2022-09-09 17:34 ` Florian Fainelli
2022-09-11 12:19 ` Vladimir Oltean
2022-09-09 8:51 ` [PATCH net-next v8 2/6] net: dsa: Add convenience functions for frame handling Mattias Forsblad
2022-09-11 13:27 ` Vladimir Oltean
2022-09-09 8:51 ` [PATCH net-next v8 3/6] net: dsa: Introduce dsa tagger data operation Mattias Forsblad
2022-09-09 17:35 ` Florian Fainelli
2022-09-11 13:46 ` Vladimir Oltean [this message]
2022-09-09 8:51 ` [PATCH net-next v8 4/6] net: dsa: mv88e6xxxx: Add RMU functionality Mattias Forsblad
2022-09-09 13:43 ` kernel test robot
2022-09-11 14:11 ` Vladimir Oltean
2022-09-09 8:51 ` [PATCH net-next v8 5/6] net: dsa: mv88e6xxx: rmon: Use RMU for reading RMON data Mattias Forsblad
2022-09-09 8:51 ` [PATCH net-next v8 6/6] net: dsa: qca8k: Use new convenience functions Mattias Forsblad
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=20220911134624.24a5pjlw77z6b7f3@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=mattias.forsblad@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.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