From: Teco Boot <teco@inf-net.nl>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
Steven Barth <cyrus@openwrt.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] IPv6 address assignment and naming
Date: Fri, 16 Aug 2013 23:39:46 +0200 [thread overview]
Message-ID: <3A55505F-43AD-4D72-A5CA-5DFFB03FDD17@inf-net.nl> (raw)
In-Reply-To: <CAA93jw4x5o3OvxVwBvmU6PHW9wRKYxy=pVKb5Dzbhnx5cAjwfA@mail.gmail.com>
The backtraces were not caused by the ip6_subtrees patch. It is Ubuntu that upgraded me to 3.8.0.28, with some free bugs. I went back to 3.8.0.27. No problems since then.
Teco
Op 16 aug. 2013, om 23:35 heeft Dave Taht <dave.taht@gmail.com> het volgende geschreven:
>
>
>
> On Fri, Aug 16, 2013 at 2:21 PM, Teco Boot <teco@inf-net.nl> wrote:
> The IPv6 subtrees in on its way :-). After 3.11 we can ask for backports.
>
> I folded it into cerowrt 3.10.7-1 just now. No noise on the patch. I was scared by some of the backtraces you posted, so I'd like to keep the testing simple for a while... and...
>
> I still have the ADSL htb fixes to fold back in from 3.11 to 3.10, to massively update cisco's pie implementation, and to make one more tweak to codel, before I do anything other than compile testing, personally.
>
> Probably will be a couple days.
>
> I have no idea the state of the babel branch on this stuff. My own use case is a system with multiple 6rd, 6in4, 6to4 tunnels in play....
>
> One of my concerns was that: is there an easy way to detect at runtime via netlink if subtrees was working correctly or not?
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-08-16 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 19:13 Dave Taht
2013-08-16 21:21 ` Teco Boot
2013-08-16 21:35 ` Dave Taht
2013-08-16 21:39 ` Teco Boot [this message]
2013-08-16 22:08 ` Hannes Frederic Sowa
2013-08-17 14:53 ` Steven Barth
2013-08-17 17:04 ` Teco Boot
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A55505F-43AD-4D72-A5CA-5DFFB03FDD17@inf-net.nl \
--to=teco@inf-net.nl \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.org \
--cc=dave.taht@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=nbd@nbd.name \
/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