[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180723.093245.1883999792575475458.davem@davemloft.net>
Date: Mon, 23 Jul 2018 09:32:45 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: nikolay@...ulusnetworks.com
Cc: netdev@...r.kernel.org, roopa@...ulusnetworks.com,
anuradhak@...ulusnetworks.com, wkok@...ulusnetworks.com,
bridge@...ts.linux-foundation.org, stephen@...workplumber.org,
makita.toshiaki@....ntt.co.jp
Subject: Re: [PATCH net-next v3 0/2] net: bridge: add support for backup
port
From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Date: Mon, 23 Jul 2018 11:16:57 +0300
> This set introduces a new bridge port option that allows any port to have
> any other port (in the same bridge of course) as its backup and traffic
> will be forwarded to the backup port when the primary goes down. This is
> mainly used in MLAG and EVPN setups where we have peerlink path which is
> a backup of many (or even all) ports and is a participating bridge port
> itself. There's more detailed information in patch 02. Patch 01 just
> prepares the port sysfs code for options that take raw value. The main
> issues that this set solves are scalability and fallback latency.
...
Series applied, thanks Nikolay.
Powered by blists - more mailing lists