From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Richter <tmricht@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] iproute vxlan add support for fdb replace command
Date: Sun, 4 Aug 2013 11:57:51 -0700 [thread overview]
Message-ID: <20130804115751.0bf8b584@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1375165001-6776-1-git-send-email-tmricht@linux.vnet.ibm.com>
On Tue, 30 Jul 2013 08:16:41 +0200
Thomas Richter <tmricht@linux.vnet.ibm.com> wrote:
> Add support for the bridge fdb replace command to replace an
> existing entry in the vxlan device driver forwarding data base.
> The entry is identified with its unicast mac address and its
> corresponding remote destination information is updated.
>
> This is useful for virtual machine migration and replaces the
> bridge fdb del and bridge fdb add commands.
>
> It follows the same interface as ip neigh replace commands.
>
> Signed-off-by: Thomas Richter <tmricht@linux.vnet.ibm.com>
Applied to master for next release.
prev parent reply other threads:[~2013-08-04 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 6:16 [PATCH] iproute vxlan add support for fdb replace command Thomas Richter
2013-08-04 18:57 ` Stephen Hemminger [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=20130804115751.0bf8b584@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=tmricht@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).