From: Jiri Benc <jbenc@redhat.com>
To: oc <oc@yunify.com>
Cc: davem@davemloft.net,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Subject: [PATCH] vxlan: only reduce known arp boardcast request to support, virtual IP
Date: Tue, 12 Sep 2017 13:51:44 +0200 [thread overview]
Message-ID: <20170912135144.2c83bef5@griffin> (raw)
In-Reply-To: <2c1bfd7d-5fe7-d492-2396-71deaeb14244@yunify.com>
On Tue, 12 Sep 2017 11:26:49 +0800, oc wrote:
> The purpose of vxlan arp reduce feature is to reply the boardcast
> arp request in vtep instead of sending it out to save traffic.
> The current implemention drops arp packet, if the ip cannot be
> found in neigh table. In the case of virtual IP address, user
> defines IP address without management from SDN controller. The IP
> address does not exist in neigh table, so the arp boardcast request
> from a client can not be sent to the server who owns the virtual IP
> address.
>
> This patch allow the arp request to be sent out if:
> 1. not arp boardcast request
> 2. cannot be found in neigh table
> 3. arp record status is not NUD_CONNECTED
>
> The user defined of virtual IP address works while arp reduce still
> suppress the arp boardcast for IP address managed by SDN controller
> with this patch.
Your patch is whitespace damaged, does not conform to the kernel coding
style and the email does not have your full name in the From header.
As for the patch itself, you're changing existing functionality that
people may depend on and thus a new config option is needed to enable
the behavior.
Jiri
prev parent reply other threads:[~2017-09-12 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 3:26 Subject: [PATCH] vxlan: only reduce known arp boardcast request to support, virtual IP oc
2017-09-12 11:51 ` Jiri Benc [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=20170912135144.2c83bef5@griffin \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oc@yunify.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).