Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Beating Bufferbloat in 2012!
Date: Wed, 7 Dec 2011 05:20:19 +0100	[thread overview]
Message-ID: <CAA93jw5j5r2UsYuVZOtF5p2NBQcA6m99P9-H3Vdz5O8VUeStpA@mail.gmail.com> (raw)

There is a post mortem on what we did right and wrong with cerowrt
versions rc1 through rc7 over on the cerowrt-devel list.

https://lists.bufferbloat.net/pipermail/cerowrt-devel/2011-December/thread.html

If you are a past, present, or future stakeholder in this sub-project
I urge you to participate over there.

I need to stress that that was/is always intended to be a 'sub' project
of bufferbloat.net's, to conduct R&D into what was going on on the
internet edge, and we learned - and fixed - a lot of problems,
some solutions for which has been pushed upstream already, and
are becoming more widely available.

There are *many* other bloat-related problems that I'd like us to be trying to
address in the coming year. While I (and jim) are going to try to
touch upon them here, I'm very interested in the opinions and thoughts
of those on this list.

I miss the heyday of the bloat list, where we had wide-ranging
discussions of absolutely everything of relevance to bufferbloat.

I mean, go back and review march-august. Wow.

https://lists.bufferbloat.net/pipermail/bloat/

What did we forget about? What opinions have changed?
What was easy? What seems to be hard?

What did we do right and wrong this year? And what can we do
better, next year?

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

                 reply	other threads:[~2011-12-07  4:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw5j5r2UsYuVZOtF5p2NBQcA6m99P9-H3Vdz5O8VUeStpA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@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