From: David Miller <davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org, wkok@cumulusnetworks.com,
anuradhak@cumulusnetworks.com
Subject: Re: [Bridge] [PATCH net-next v3 0/2] net: bridge: add support for backup port
Date: Mon, 23 Jul 2018 09:32:45 -0700 (PDT) [thread overview]
Message-ID: <20180723.093245.1883999792575475458.davem@davemloft.net> (raw)
In-Reply-To: <20180723081659.21986-1-nikolay@cumulusnetworks.com>
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.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.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
anuradhak@cumulusnetworks.com, wkok@cumulusnetworks.com,
bridge@lists.linux-foundation.org, stephen@networkplumber.org,
makita.toshiaki@lab.ntt.co.jp
Subject: Re: [PATCH net-next v3 0/2] net: bridge: add support for backup port
Date: Mon, 23 Jul 2018 09:32:45 -0700 (PDT) [thread overview]
Message-ID: <20180723.093245.1883999792575475458.davem@davemloft.net> (raw)
In-Reply-To: <20180723081659.21986-1-nikolay@cumulusnetworks.com>
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.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.
next prev parent reply other threads:[~2018-07-23 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 8:16 [Bridge] [PATCH net-next v3 0/2] net: bridge: add support for backup port Nikolay Aleksandrov
2018-07-23 8:16 ` Nikolay Aleksandrov
2018-07-23 8:16 ` [Bridge] [PATCH 1/2 net-next v3] net: bridge: add support for raw sysfs port options Nikolay Aleksandrov
2018-07-23 8:16 ` Nikolay Aleksandrov
2018-07-23 8:16 ` [Bridge] [PATCH 2/2 net-next v3] net: bridge: add support for backup port Nikolay Aleksandrov
2018-07-23 8:16 ` Nikolay Aleksandrov
2018-07-23 16:32 ` David Miller [this message]
2018-07-23 16:32 ` [PATCH net-next v3 0/2] " David Miller
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=20180723.093245.1883999792575475458.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=anuradhak@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=wkok@cumulusnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.