Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Dropping features from cerowrt
Date: Sat, 24 Dec 2011 21:26:16 +0100	[thread overview]
Message-ID: <CAA93jw7pGu_ovi1po1hzAkiZmJ2-bGr9EpPcyWcj81fiOCVckg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4rqGA4Rm1FPvbn6i-64PHCdVdGwnm4-EBDMzJJH6COxw@mail.gmail.com>

> I'd like a tool that can analyze the burstyness of flows. We have
> (with things like TSO/GSO, no AQM, wireless aggregation, and the
> architecture of many TCP stacks) introduced, effectively,

Didn't finish this sentence. ... "something worse than jumbo-packets,
which (thankfully) never escaped the data center. "

>> PS I was able to install rc6 trivially, and got it to work nicely on a WNCR3700v2. Your install instructions for OSX were impeccable. I now need to decide whether to heed your advice (not to inflict these builds on spouses and small children) or switch over to the stock Openwrt build.
>
> Heh. I could have said this better. (At the time I was not a happy
> guy). My hope would be for those interested in this project to
> evaluate a stable cerowrt release for day-to-day use, make sure it's
> fully compatible with their wives and small children FIRST, then
> deploy for day to day. :)

And I realize that I wasn't being politically correct, here. 'spouses
and small children'. Fixing bufferbloat is an equal opportunity
problem.

in my case I drive myself crazy with the need to be on the internet -
and debug a router. I can't file bugs - or look at them, after
knocking myself off the net. I miss gnats, and I like using org-mode
to manage my stack, and wish the world had more off-line applications
like git. Git is a life saver.


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net

      reply	other threads:[~2011-12-24 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-24 17:05 Richard Brown
2011-12-24 19:35 ` Dave Taht
2011-12-24 20:26   ` Dave Taht [this message]

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=CAA93jw7pGu_ovi1po1hzAkiZmJ2-bGr9EpPcyWcj81fiOCVckg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richard.e.brown@dartware.com \
    /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