From: David Miller <davem@davemloft.net>
To: tmricht@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH 1/2 V2] vxlan fdb replace an existing entry
Date: Tue, 23 Jul 2013 16:36:35 -0700 (PDT) [thread overview]
Message-ID: <20130723.163635.1418496776410988221.davem@davemloft.net> (raw)
In-Reply-To: <1374247208-8226-1-git-send-email-tmricht@linux.vnet.ibm.com>
From: Thomas Richter <tmricht@linux.vnet.ibm.com>
Date: Fri, 19 Jul 2013 17:20:07 +0200
> Add support to replace an existing entry found in the
> vxlan fdb database. The entry in question is identified
> by its unicast mac address and the destination information
> is changed. If the entry is not found, it is added in the
> forwarding database. This is similar to changing an entry
> in the neighbour table.
>
> Multicast mac addresses can not be changed with the replace
> option.
>
> This is useful for virtual machine migration when the
> destination of a target virtual machine changes. The replace
> feature can be used instead of delete followed by add.
>
> Resubmitted because net-next was closed last week.
>
> Signed-off-by: Thomas Richter <tmricht@linux.vnet.ibm.com>
Applied.
next prev parent reply other threads:[~2013-07-23 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 15:20 [PATCH 1/2 V2] vxlan fdb replace an existing entry Thomas Richter
2013-07-19 15:20 ` [PATCH 2/2 V2] macvlan fdb replace support Thomas Richter
2013-07-19 16:18 ` Stephen Hemminger
2013-07-22 13:16 ` Thomas-Mich Richter
2013-07-23 23:36 ` David Miller
2013-07-23 23:36 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-12 7:10 [PATCH 1/2 V2] vxlan fdb replace an existing entry Thomas Richter
2013-07-12 23:11 ` 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=20130723.163635.1418496776410988221.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).