From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
netdev@vger.kernel.org
Subject: Re: [PATCH v5 net-next 4/5] net: dsa: mv88e6xxx: Link aggregation support
Date: Thu, 14 Jan 2021 02:50:16 +0200 [thread overview]
Message-ID: <20210114005016.2xgdexp2vkp3xmst@skbuf> (raw)
In-Reply-To: <20210113084255.22675-5-tobias@waldekranz.com>
On Wed, Jan 13, 2021 at 09:42:54AM +0100, Tobias Waldekranz wrote:
> Support offloading of LAGs to hardware. LAGs may be attached to a
> bridge in which case VLANs, multicast groups, etc. are also offloaded
> as usual.
>
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
> ---
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
> +static bool mv88e6xxx_lag_can_offload(struct dsa_switch *ds,
> + struct net_device *lag,
> + struct netdev_lag_upper_info *info)
> +{
> + struct dsa_port *dp;
> + int id, members = 0;
> +
> + id = dsa_lag_id(ds->dst, lag);
> + if (id < 0 || id >= ds->num_lag_ids)
This "id >= ds->num_lag_ids" condition is there just in the off chance
that the mv88e6xxx could be bridged in the same DSA tree with another
device that reports a higher ds->num_lag_ids such that dst->lags_len
picks up that larger maximum, but otherwise the two switches have the
same understanding of the LAG ID, and are compatible with one another?
That sounds... plausible?
next prev parent reply other threads:[~2021-01-14 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 8:42 [PATCH v5 net-next 0/5] net: dsa: Link aggregation support Tobias Waldekranz
2021-01-13 8:42 ` [PATCH v5 net-next 1/5] net: bonding: Notify ports about their initial state Tobias Waldekranz
2021-01-13 8:42 ` [PATCH v5 net-next 2/5] net: dsa: Don't offload port attributes on standalone ports Tobias Waldekranz
2021-01-14 0:36 ` Vladimir Oltean
2021-01-13 8:42 ` [PATCH v5 net-next 3/5] net: dsa: Link aggregation support Tobias Waldekranz
2021-01-13 8:42 ` [PATCH v5 net-next 4/5] net: dsa: mv88e6xxx: " Tobias Waldekranz
2021-01-14 0:50 ` Vladimir Oltean [this message]
2021-01-14 8:05 ` Tobias Waldekranz
2021-01-13 8:42 ` [PATCH v5 net-next 5/5] net: dsa: tag_dsa: Support reception of packets from LAG devices Tobias Waldekranz
2021-01-15 1:30 ` [PATCH v5 net-next 0/5] net: dsa: Link aggregation support 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=20210114005016.2xgdexp2vkp3xmst@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vfalico@gmail.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