netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: netdev@vger.kernel.org
Cc: jhs@mojatatu.com, David Ahern <dsahern@gmail.com>
Subject: [PATCH net-next 0/3] net: flush neighbor entries when carrier is off
Date: Sun,  5 Nov 2017 22:57:50 -0800	[thread overview]
Message-ID: <1509951473-25990-1-git-send-email-dsahern@gmail.com> (raw)

Commit a6db4494d218c ("net: ipv4: Consider failed nexthops in multipath
routes") added support for checking neighbor state when selecting a path
for multipath route lookups. It works but incurs a delay waiting for
the neighbor entry to timeout. Improve the path selection by flushing
non-permanent neighbor entries when carrier is off.

David Ahern (3):
  net: neigh: Add helper to flush entries on carrier down
  net: ipv4: flush neighbor entries when carrier is off
  net: ipv6: flush neighbor entries when carrier is off

 include/net/neighbour.h |  1 +
 net/core/neighbour.c    | 26 ++++++++++++++++++++++----
 net/ipv4/fib_frontend.c |  7 +++++--
 net/ipv6/addrconf.c     |  3 +++
 4 files changed, 31 insertions(+), 6 deletions(-)

-- 
2.1.4

             reply	other threads:[~2017-11-06  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06  6:57 David Ahern [this message]
2017-11-06  6:57 ` [PATCH net-next 1/3] net: neigh: Add helper to flush entries on carrier down David Ahern
2017-11-06  6:57 ` [PATCH net-next 2/3] net: ipv4: flush neighbor entries when carrier is off David Ahern
2017-11-06 10:47   ` Ido Schimmel
2017-11-06 14:49     ` David Ahern
2017-11-07  5:29       ` David Ahern
2017-11-06  6:57 ` [PATCH net-next 3/3] net: ipv6: " David Ahern
     [not found] ` <CAKYOsXz3RFqbzENy1rz8kjsr3aF0u2kxBHrSQ3uNfFfQTWbJRQ@mail.gmail.com>
2017-11-08  3:39   ` [PATCH net-next 0/3] net: " 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=1509951473-25990-1-git-send-email-dsahern@gmail.com \
    --to=dsahern@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    /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).