From: David Miller <davem@davemloft.net>
To: dsahern@kernel.org
Cc: netdev@vger.kernel.org, alan.maguire@oracle.com,
jwestfall@surrealistic.net, dsahern@gmail.com
Subject: Re: [PATCH v2 net] neighbor: Call __ipv4_neigh_lookup_noref in neigh_xmit
Date: Sun, 05 May 2019 10:42:48 -0700 (PDT) [thread overview]
Message-ID: <20190505.104248.1454328009154159060.davem@davemloft.net> (raw)
In-Reply-To: <20190503155501.28182-1-dsahern@kernel.org>
From: David Ahern <dsahern@kernel.org>
Date: Fri, 3 May 2019 08:55:01 -0700
> From: David Ahern <dsahern@gmail.com>
>
> Commit cd9ff4de0107 changed the key for IFF_POINTOPOINT devices to
> INADDR_ANY, but neigh_xmit which is used for MPLS encapsulations was not
> updated to use the altered key. The result is that every packet Tx does
> a lookup on the gateway address which does not find an entry, a new one
> is created only to find the existing one in the table right before the
> insert since arp_constructor was updated to reset the primary key. This
> is seen in the allocs and destroys counters:
> ip -s -4 ntable show | head -10 | grep alloc
>
> which increase for each packet showing the unnecessary overhread.
>
> Fix by having neigh_xmit use __ipv4_neigh_lookup_noref for NEIGH_ARP_TABLE.
> Define __ipv4_neigh_lookup_noref in case CONFIG_INET is not set.
>
> v2
> - define __ipv4_neigh_lookup_noref in case CONFIG_INET is not set as
> reported by kbuild test robot
>
> Fixes: cd9ff4de0107 ("ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY")
> Reported-by: Alan Maguire <alan.maguire@oracle.com>
> Signed-off-by: David Ahern <dsahern@gmail.com>
>
> Signed-off-by: David Ahern <dsahern@gmail.com>
Double signoff and this patch doesn't apply to the net tree.
next prev parent reply other threads:[~2019-05-05 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 15:55 [PATCH v2 net] neighbor: Call __ipv4_neigh_lookup_noref in neigh_xmit David Ahern
2019-05-05 17:42 ` David Miller [this message]
2019-05-05 17:43 ` David Ahern
2019-05-05 17:53 ` 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=20190505.104248.1454328009154159060.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan.maguire@oracle.com \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=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).