From: David Miller <davem@davemloft.net>
To: mkubecek@suse.cz
Cc: jbenc@redhat.com, netdev@vger.kernel.org,
hannes@stressinduktion.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH v2 net-next] ipv6: router reachability probing
Date: Wed, 11 Dec 2013 19:56:51 -0500 (EST) [thread overview]
Message-ID: <20131211.195651.959794720995269703.davem@davemloft.net> (raw)
In-Reply-To: <20131211231236.GA8953@lion.mk-sys.cz>
From: Michal Kubecek <mkubecek@suse.cz>
Date: Thu, 12 Dec 2013 00:12:36 +0100
> Is it really the case in current mainline kernels? In my tests, this
> behaviour in 3.0 kernel (SLES 11 SP3) was caused by the reference held
> by struct dst_entry which caused that in neigh_periodic_work(),
> n->refcnt was always bigger than one so that the neighbour entry was
> never cleaned up. But when I tested with 3.11.6 (OpenSuSE 13.1) where
> neighbour is no longer cached in struct dst_entry, the neighbour was
> cleaned up eventually and new lookup was performed.
The detachment of neighbours from route entires has had many consequences,
both desirable and undesirable. This happens to be one of the former,
fortunately :-)
next prev parent reply other threads:[~2013-12-12 0:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 12:48 [PATCH v2 net-next] ipv6: router reachability probing Jiri Benc
2013-12-11 19:10 ` Hannes Frederic Sowa
2013-12-11 21:03 ` David Miller
2013-12-11 23:12 ` Michal Kubecek
2013-12-12 0:56 ` David Miller [this message]
2013-12-12 1:26 ` Hannes Frederic Sowa
2013-12-12 1:21 ` Hannes Frederic Sowa
2013-12-12 9:10 ` Michal Kubecek
2013-12-12 19:08 ` Hannes Frederic Sowa
2013-12-13 12:51 ` Michal Kubecek
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=20131211.195651.959794720995269703.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).