netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Westfall <jwestfall@surrealistic.net>
To: netdev@vger.kernel.org
Cc: Jim Westfall <jwestfall@surrealistic.net>
Subject: [PATCH v2 0/2] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY
Date: Sun, 14 Jan 2018 04:18:49 -0800	[thread overview]
Message-ID: <20180114121851.2659-1-jwestfall@surrealistic.net> (raw)

This used to be the previous behavior in older kernels but became broken in
a263b3093641f (ipv4: Make neigh lookups directly in output packet path)
and then later removed because it was broken in 0bb4087cbec0 (ipv4: Fix neigh
lookup keying over loopback/point-to-point devices)

Not having this results in there being an arp entry for every remote ip
address that the device talks to.  Given a fairly active device it can
cause the arp table to become huge and/or having to add/purge large number
of entires to keep within table size thresholds.

$ ip -4 neigh show nud noarp | grep tun | wc -l
55850

$ lnstat -k arp_cache:entries,arp_cache:allocs,arp_cache:destroys -c 10
arp_cach|arp_cach|arp_cach|
 entries|  allocs|destroys|
   81493|620166816|620126069|
  101867|   10186|       0|
  113854|    5993|       0|
  118773|    2459|       0|
   27937|   18579|   63998|
   39256|    5659|       0|
   56231|    8487|       0|
   65602|    4685|       0|
   79697|    7047|       0|
   90733|    5517|       0|

v2: 
 - fixes coding style issues

Jim Westfall (2):
  net: Allow neigh contructor functions ability to modify the
    primary_key
  ipv4: Make neigh lookup keys for loopback/point-to-point devices be
    INADDR_ANY

 include/net/arp.h    | 3 +++
 net/core/neighbour.c | 4 ++--
 net/ipv4/arp.c       | 7 ++++++-
 3 files changed, 11 insertions(+), 3 deletions(-)

-- 
2.15.1

             reply	other threads:[~2018-01-14 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14 12:18 Jim Westfall [this message]
2018-01-14 12:18 ` [PATCH v2 1/2] net: Allow neigh contructor functions ability to modify the primary_key Jim Westfall
2018-01-14 12:18 ` [PATCH v2 2/2] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY Jim Westfall
2018-01-15 19:54 ` [PATCH v2 0/2] " David Miller
2018-01-15 21:42   ` Jim Westfall
2018-01-15 21:59     ` 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=20180114121851.2659-1-jwestfall@surrealistic.net \
    --to=jwestfall@surrealistic.net \
    --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).