[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170807.144949.1849322815118190718.davem@davemloft.net>
Date: Mon, 07 Aug 2017 14:49:49 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: arkadis@...lanox.com
Cc: netdev@...r.kernel.org, jiri@...nulli.us, ivecera@...hat.com,
f.fainelli@...il.com, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com, Woojung.Huh@...rochip.com,
mlxsw@...lanox.com
Subject: Re: [PATCH net-next v3 00/13] Update DSA's FDB API and perform
switchdev cleanup
From: Arkadi Sharshevsky <arkadis@...lanox.com>
Date: Sun, 6 Aug 2017 16:15:38 +0300
> The patchset adds support for configuring static FDB entries via the
> switchdev notification chain. The current method for FDB configuration
> uses the switchdev's bridge bypass implementation. In order to support
> this legacy way and to perform the switchdev cleanup, the implementation
> is moved inside DSA.
>
> The DSA drivers cannot sync the software bridge with hardware learned
> entries and use the switchdev's implementation of bypass FDB dumping.
> Because they are the only ones using this functionality, the fdb_dump
> implementation is moved from switchdev code into DSA.
>
> Finally after this changes a major cleanup in switchdev can be done.
> ---
> Please see individual patches for patch specific change logs.
> v1->v2
> - Split MDB/vlan dump removal into core/driver removal.
>
> v2->v3
> - The self implementation for FDB add/del is moved inside DSA.
Series applied, thank you.
Powered by blists - more mailing lists