Netdev List
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: DENG Qingfang <dqfext@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, "Andrew Lunn" <andrew@lunn.ch>,
	"Marek Behún" <kabel@kernel.org>,
	"Tobias Waldekranz" <tobias@waldekranz.com>,
	"Vivien Didelot" <vivien.didelot@gmail.com>,
	"Russell King - ARM Linux admin" <linux@armlinux.org.uk>,
	"Florian Fainelli" <f.fainelli@gmail.com>
Subject: Re: DSA .port_{f,m}db_{add,del} with offloaded LAG interface on mv88e6xxx
Date: Mon, 19 Jul 2021 15:45:13 +0300	[thread overview]
Message-ID: <20210719124513.f6rshjaressm5jhz@skbuf> (raw)
In-Reply-To: <CALW65jZoaYYycAApviuQjiOTNuG9sfSpGZ1izRgJhj4M-gfDyQ@mail.gmail.com>

Hi Qingfang,

On Mon, Jul 19, 2021 at 08:22:01PM +0800, DENG Qingfang wrote:
> Hi,
> 
> What happens if a FDB entry is added manually to an offloaded LAG
> interface? Does DSA core simply call .port_fdb_add with the member
> ports in the LAG?
> 
> I'm asking because there is a trunk field in struct
> mv88e6xxx_atu_entry, when it is true, the portvec is actually the
> trunk ID.
> As the current implementation (mv88e6xxx_port_db_load_purge) does not
> use this field, it probably won't work.
> 
> Regards,
> Qingfang

This is not supported at the moment.
Coincidentally or not, I am currently working on refactoring the DSA
handler for SWITCHDEV_FDB_ADD_TO_DEVICE to remove some of the technical
debt (in particular, local FDB entries pointing towards the bridge do
not work in all situations when combined with FDB replays). One of the
extra features of the new implementation will be a new .lag_fdb_add()
method in struct dsa_switch_ops.

      reply	other threads:[~2021-07-19 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 12:22 DSA .port_{f,m}db_{add,del} with offloaded LAG interface on mv88e6xxx DENG Qingfang
2021-07-19 12:45 ` Vladimir Oltean [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=20210719124513.f6rshjaressm5jhz@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=dqfext@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=kabel@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=tobias@waldekranz.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