Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Justin McCann <jneilm@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Re: Mice [was Re: QoS for system critical packets on wireless]
Date: Wed, 22 Jun 2011 14:42:22 -0600	[thread overview]
Message-ID: <BANLkTi=R2ft2MTd6W9RHhQFBH4S+WeFraw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=aj4quHB3z3Je39BSwct-8Or15WA@mail.gmail.com>

OK, so I've gone and updated the related wiki page to indicate more
of what I'd actually meant. Still need a good analogy though...

Secondly you've given me an idea towards actively tracking mice-y
short flows using something like conntrack or simply getting stats on
syns, synacks,fins, finacks which ought to be interesting in itself.
One problem I'd already found in the openwrt defaults was that it does
severe rate limiting of syns by default - 25!!!??? which I only found
by trying to access the top 100 web sites all at the same time and
being totally befuddled by the results. (this test is also in my
Diffserv repo)

Thirdly, although the iptables implementation of diffserv was
straightforward and
easy to describe, and the proposal for enhancing iptables to be
performant equally clear and straightforward, it's beginning to appear
that most of the functionality I proposed in the first draft of the
diffserv rfc belongs in the 'tc' subsystem, not in iptables.

I'm really glad I wrote it down and am grateful for the feedback both
public and private thus far.


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

  reply	other threads:[~2011-06-22 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 19:39 Justin McCann
2011-06-22 20:11 ` Dave Taht
2011-06-22 20:42   ` Dave Taht [this message]
2011-06-22 20:59   ` Jonathan Morton
2011-06-22 21:06     ` Dave Taht
2011-06-23  2:47       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTi=R2ft2MTd6W9RHhQFBH4S+WeFraw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=jneilm@gmail.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