CoDel AQM discussions
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
	bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] Latest codel, fq_codel, and pie sim study from cablelabs now available
Date: Wed, 01 May 2013 19:20:06 -0700	[thread overview]
Message-ID: <5181CD56.9050501@superduper.net> (raw)
In-Reply-To: <86AA48E0-B5CD-4A94-AF2B-D75178E8C660@gmail.com>

Or one could use more queues in SFQ, so that the chance of 2 streams 
sharing a queue is small. Even perhaps use a different strategy than 
hashing to distribute traffic to queues, although whatever strategy is 
used needs to be resistant to DoS attacks. Or one could classify the 
VoIP traffic and prioritise that. Another possibility is a heuristic 
approach - don't mix long lived bulk data streams in the same bucket as 
others.

Simon

On Wed 01 May 2013 05:00:27 PM PDT, Jonathan Morton wrote:
>
> On 1 May, 2013, at 11:26 pm, Simon Barber wrote:
>
>> Interesting to note that sfq-codel's reaction to a non conforming flow is of course to start dropping more aggressively to make it conform, leading to the high loss rates for whatever is hashed together with a VoIP flow that does not reduce it's bandwidth.
>>
>> One downside to SFQ really.
>
> The only real solution, for the scenario where this happens, would be to somehow identify all the BitTorrent traffic and stuff it into a single bucket, where it has to compete on equal terms with the single VoIP flow.  The big unanswered question is then: can this realistically be done?  Does BitTorrent traffic get marked as the bulk, low priority traffic it is, for example?

  reply	other threads:[~2013-05-02  2:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 11:23 [Codel] " Dave Taht
2013-05-01 20:26 ` [Codel] [Bloat] " Simon Barber
2013-05-02  0:00   ` Jonathan Morton
2013-05-02  2:20     ` Simon Barber [this message]
2013-05-02  4:59       ` Andrew McGregor
2013-05-02 12:04       ` Jonathan Morton
2013-05-02 13:29         ` Simon Perreault
2013-05-14  2:26         ` Dan Siemon
2013-05-14  4:56           ` Tristan Seligmann
2013-05-14 10:24             ` Dave Taht
2013-05-14 13:02               ` Eric Dumazet
2013-06-11 18:19             ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-14 12:12           ` [Codel] " Jesper Dangaard Brouer
2013-05-06 17:54       ` Jesper Dangaard Brouer
2013-05-06 18:46         ` Jonathan Morton
2013-05-06 20:47           ` Jesper Dangaard Brouer
2013-05-07 16:22             ` Greg White
2013-05-07 13:31       ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-07 16:30         ` [Codel] [Bloat] [Cerowrt-devel] " Greg White
2013-05-07 19:56           ` [Codel] [Bloat] " Wes Felter
2013-05-07 20:30             ` Eric Dumazet
2013-05-08 22:25               ` Dave Taht
2013-05-08 22:54                 ` Eric Dumazet
2013-05-09  1:45                   ` Andrew McGregor

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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=5181CD56.9050501@superduper.net \
    --to=simon@superduper.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=codel@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