Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] AQM and ADSL
Date: Tue, 13 Aug 2013 21:42:47 +0100	[thread overview]
Message-ID: <D790027B-21C1-4D3D-84C2-48E51B0D53D0@imap.cc> (raw)
In-Reply-To: <CAA93jw7ji97fOz-DQBp+BKFu8VBjMk_-uCVuU3PWChhv4R-6Gg@mail.gmail.com>

Thank you. That is a useful explanation.

Incorporation requests

Gargoyle AAC
htb fixes.


On 13 Aug 2013, at 21:33, Dave Taht <dave.taht@gmail.com> wrote:

> On Tue, Aug 13, 2013 at 12:40 PM, Fred Stratton <fredstratton@imap.cc> wrote:
> 
>>> 
>>> DT has taken to stealth with his releases.
> 
> Heh. No, these are not releases. If I don't get a chance to do some
> testing I don't post their existence to the list.
> 
> I don't mind people being eager and willing to test 'em without me
> doing so, tho.
> 
> To explain, I do what's called "continuous integration" whenever
> possible (see wikipedia)
> 
> Big triggers for that are new kernel releases (like 3.10.6), fixes
> like the boatload that felix just landed for the ethernet and the wifi
> aggregation rework, and tossing in a new version of the codel patches,
> and tossing in the AQM stuff that sebastian just did - and all that
> landed in 3.10.6-1.
> 
> Merely getting this stuff to compile is often a chore. In fact, it
> took me all day to get all that to work... and my only spare router I
> dare sacrifice (the other 4 in the testbed are doing some benchmarks
> as I write) is still in my suitcase and in the car.
> 
> Usually I get around to announcing a "development release" once it's
> been tested for a little while, at least a quick check, and preferably
> a couple hours under heavy load, and usually that will be at least a
> -3. I generally try to stay away from X.Y.0 and wait for X.Y.1...
> 
> We still have a few things left to fold into this kernel - notably the
> new htb patches from jesper and to backport a few other fixes from
> net-next, and it looks like the changes to the AQM thing need a
> smarter radio box in the gui(?). I'm also trying to freeze the ubnt
> picostation and nanostation on the same stuff (and what's causing even
> more delay is trying to get a guruplug and edgerouter booted with it
> too. I've always resisted expanding the scope of the cerowrt project
> to more hardware, but I need two higher power boxes to drive some
> tests with desparately)
> 
> I'm off to do my laundry in a bit, and will return with fresh clothes
> and that router this evening.
> 
> I would very much like to get to a new "stable" release this month,
> it's been far too long since the last one! But to do that we have to
> have zero crash bugs, and be "feature complete". I think we are close
> to zero crashes (but felix fiddling with the ethernet and the wifi
> recently scares me and I still haven't checked to see if sysupgrade
> worked in a couple releases (I flash via tftp usually)), but there are
> some nagging features that I'd like to get in there. Like this one.
> Keep plugging away, please.
> 
> Are there any other must-have features for this puppy? I've been
> looking over gargoyle's ACC code in particular.
> 
>>> 
>>>> 
>>>>     So 3.10.6-1 fails with sysupgrade?
>>>> 
>>>> best
>>>>     Sebastian
>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Cerowrt-devel mailing list
>>>>> Cerowrt-devel@lists.bufferbloat.net
>>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>> 
>>> 
>> 
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 
> 
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html


  reply	other threads:[~2013-08-13 20:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0CA86B40-F485-4164-B183-E0A53D800FC8@imap.cc>
2013-08-13 19:40 ` Fred Stratton
2013-08-13 20:33   ` Dave Taht
2013-08-13 20:42     ` Fred Stratton [this message]
2013-08-14 12:26     ` Sebastian Moeller
     [not found]   ` <AAD163FD-45A1-40DF-82B9-80DB1AC150DE@gmx.de>
2013-08-14 12:01     ` Fred Stratton
2013-08-14 13:31       ` Sebastian Moeller
2013-08-14 13:38         ` [Cerowrt-devel] Fwd: " Fred Stratton
     [not found]         ` <32AAB67F-48B4-4504-8772-CF4229CB11B8@imap.cc>
2013-08-14 13:39           ` Fred Stratton
2013-08-14 14:18           ` [Cerowrt-devel] " Sebastian Moeller
2013-08-14 14:28             ` Fred Stratton
2013-08-14 15:09               ` Sebastian Moeller
2013-08-14 15:37                 ` Fred Stratton
2013-08-13 15:28 Fred Stratton
2013-08-13 18:53 ` Sebastian Moeller
2013-08-13 19:38   ` Fred Stratton

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=D790027B-21C1-4D3D-84C2-48E51B0D53D0@imap.cc \
    --to=fredstratton@imap.cc \
    --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