From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hacking on babel 1.8.3
Date: Wed, 3 Oct 2018 20:40:44 -0700 [thread overview]
Message-ID: <CAA93jw4F9FyLst7iLd9Yq3eBWzPJKiEBN2MU3kkVF+ONN9mYCA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5-0YSsj-dxU_jbxFPJW6hG4d7n7M_Hk=KXnNjSv93oyw@mail.gmail.com>
never mind. I got the inline qsort to appear to work in the
babeld-xnor branch. The atomic branch is still problematic. Off to see
how to go about improving xroute import on the morrow
https://github.com/dtaht/babeld/commits/babeld-xnor
On Wed, Oct 3, 2018 at 3:57 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> I've been trying to deploy the latest openwrt to all ~40 routers I
> have. (I did get a reprieve on having to close the lab, but I have to
> update the whole campus as part of it).
>
> Anyway after some struggle with a bridge, I ended up being able to
> deploy openwrt to about half the campus so far. The two major blockers
> are the ipv6 issue I mentioned here, and the speed issues we've also
> discussed (though I can just throw hardware at it on 3 of the
> gateways).
>
> But I took a deep dive on some long standing issues in babel and
> finally got around to doing something about it, establishing a bug
> tracker, trying to make it faster, and do atomic routing updates and
> so on.
>
> In particular, it really looked to me as though a faster qsort would
> speed up babel
> by quite a bit but my first attempt at an inline version didn't work.
> If anyone is bored and wants to debug an enormous macro, it's here:
>
> https://github.com/dtaht/babeld/issues
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-10-04 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 22:57 Dave Taht
2018-10-04 3:40 ` Dave Taht [this message]
2018-10-04 14:27 ` Mikael Abrahamsson
2018-10-04 14:33 ` Dave Taht
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=CAA93jw4F9FyLst7iLd9Yq3eBWzPJKiEBN2MU3kkVF+ONN9mYCA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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