From: Ido Schimmel <idosch@idosch.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: jiri@resnulli.us, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
idosch@mellanox.com, davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next 2/2] net: bridge: allow to add externally learned entries from user-space
Date: Thu, 23 Mar 2017 21:47:57 +0200 [thread overview]
Message-ID: <20170323194757.GB25688@splinter.mtl.com> (raw)
In-Reply-To: <1490264833-28867-3-git-send-email-nikolay@cumulusnetworks.com>
On Thu, Mar 23, 2017 at 12:27:13PM +0200, Nikolay Aleksandrov wrote:
> The NTF_EXT_LEARNED flag was added for switchdev and externally learned
> entries, but it can also be used for entries learned via a software
> in user-space which requires dynamic entries that do not expire.
> One such case that we have is with quagga and evpn which need dynamic
> entries but also require to age them themselves.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Reviewed-by: Ido Schimmel <idosch@mellanox.com>
WARNING: multiple messages have this Message-ID (diff)
From: Ido Schimmel <idosch@idosch.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, idosch@mellanox.com, jiri@resnulli.us,
stephen@networkplumber.org, bridge@lists.linux-foundation.org,
roopa@cumulusnetworks.com, davem@davemloft.net
Subject: Re: [PATCH net-next 2/2] net: bridge: allow to add externally learned entries from user-space
Date: Thu, 23 Mar 2017 21:47:57 +0200 [thread overview]
Message-ID: <20170323194757.GB25688@splinter.mtl.com> (raw)
In-Reply-To: <1490264833-28867-3-git-send-email-nikolay@cumulusnetworks.com>
On Thu, Mar 23, 2017 at 12:27:13PM +0200, Nikolay Aleksandrov wrote:
> The NTF_EXT_LEARNED flag was added for switchdev and externally learned
> entries, but it can also be used for entries learned via a software
> in user-space which requires dynamic entries that do not expire.
> One such case that we have is with quagga and evpn which need dynamic
> entries but also require to age them themselves.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Reviewed-by: Ido Schimmel <idosch@mellanox.com>
next prev parent reply other threads:[~2017-03-23 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 10:27 [Bridge] [PATCH net-next 0/2] net: bridge: allow user-space to add ext learned entries Nikolay Aleksandrov
2017-03-23 10:27 ` Nikolay Aleksandrov
2017-03-23 10:27 ` [Bridge] [PATCH net-next 1/2] net: bridge: allow SW learn to take over HW fdb entries Nikolay Aleksandrov
2017-03-23 10:27 ` Nikolay Aleksandrov via Bridge
2017-03-23 19:47 ` [Bridge] " Ido Schimmel
2017-03-23 19:47 ` Ido Schimmel
2017-03-23 10:27 ` [Bridge] [PATCH net-next 2/2] net: bridge: allow to add externally learned entries from user-space Nikolay Aleksandrov
2017-03-23 10:27 ` Nikolay Aleksandrov
2017-03-23 19:47 ` Ido Schimmel [this message]
2017-03-23 19:47 ` Ido Schimmel
2017-03-23 12:48 ` [Bridge] [PATCH net-next 0/2] net: bridge: allow user-space to add ext learned entries Nikolay Aleksandrov
2017-03-23 12:48 ` Nikolay Aleksandrov via Bridge
2017-03-23 20:00 ` [Bridge] " Ido Schimmel
2017-03-23 20:00 ` Ido Schimmel
2017-03-24 19:31 ` [Bridge] " David Miller
2017-03-24 19:31 ` 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=20170323194757.GB25688@splinter.mtl.com \
--to=idosch@idosch.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@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.