From: David Miller <davem@davemloft.net>
To: roland@kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH/RFC] ipv6: fib: Drop cached routes with dead neighbours on fib GC
Date: Fri, 11 Jan 2013 15:50:38 -0800 (PST) [thread overview]
Message-ID: <20130111.155038.1606083912179468348.davem@davemloft.net> (raw)
In-Reply-To: <CAL1RGDVjwddbyVdkzMeXEiqFXQNECjCWAyEFK5V5oAPddfbwZA@mail.gmail.com>
From: Roland Dreier <roland@kernel.org>
Date: Fri, 11 Jan 2013 13:13:42 -0800
> In the meantime does it make sense to put a smaller bandaid in 3.8?
I want it fixed properly from the start, sorry.
> I'm pretty sure this is a regression (we never saw it with older
> kernels), probably due to some part of the route cache improvements
> you've been doing.
I do not believe this is the situation at all.
next prev parent reply other threads:[~2013-01-11 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:44 [PATCH/RFC] ipv6: fib: Drop cached routes with dead neighbours on fib GC Roland Dreier
2013-01-10 22:18 ` David Miller
2013-01-11 8:57 ` David Laight
2013-01-11 21:13 ` Roland Dreier
2013-01-11 23:50 ` David Miller [this message]
2013-01-11 13:40 ` Hannes Frederic Sowa
2013-01-11 14:01 ` Hannes Frederic Sowa
2013-01-11 21:10 ` Roland Dreier
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=20130111.155038.1606083912179468348.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roland@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).