Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Wes Felter <wmf@felter.org>
To: cerowrt-devel@lists.bufferbloat.net
Cc: codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Bloat]   Latest codel, fq_codel, and pie sim study from cablelabs now available
Date: Tue, 07 May 2013 14:56:02 -0500	[thread overview]
Message-ID: <kmbm8e$1a7$1@ger.gmane.org> (raw)
In-Reply-To: <CDAE8660.11924%g.white@cablelabs.com>

On 5/7/13 11:30 AM, Greg White wrote:
> This presumes that UDP is the only traffic that is latency sensitive (we
> also consider web traffic to be latency sensitive), and that TCP carries
> the bulk data that causes problems for latency sensitive traffic (AFAIK
> BitTorrent uTP is layered on top of UDP).
>
> I'm not sure that a TCP/UDP distinction ends up helping in the end.

I agree. We already have ToS/DiffServ so I would be hesitant to try to 
encode some other heuristic into a scheduler. (If your traffic isn't 
properly marked you can use some heuristic iptables rules to remark it, 
keeping classification orthogonal from scheduling.)

Is it time for prio_fq_codel or wfq_codel? That's what comes to mind 
when seeing the BitTorrent vs. VoIP results.

-- 
Wes Felter
IBM Research - Austin


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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 11:23 [Cerowrt-devel] " Dave Taht
2013-05-01 20:26 ` [Cerowrt-devel] [Bloat] " Simon Barber
2013-05-02  0:00   ` Jonathan Morton
2013-05-02  2:20     ` Simon Barber
2013-05-02  4:59       ` [Cerowrt-devel] [Codel] " Andrew McGregor
2013-05-02 12:04       ` [Cerowrt-devel] " Jonathan Morton
2013-05-14  2:26         ` [Cerowrt-devel] [Codel] " Dan Siemon
2013-05-14  4:56           ` [Cerowrt-devel] [Bloat] [Codel] " Tristan Seligmann
2013-05-14 10:24             ` Dave Taht
2013-05-14 13:02               ` [Cerowrt-devel] [Codel] [Bloat] " Eric Dumazet
2013-06-11 18:19             ` [Cerowrt-devel] [Bloat] [Codel] " Michael Richardson
2013-05-14 12:12           ` [Cerowrt-devel] [Codel] [Bloat] " 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       ` [Cerowrt-devel] " Michael Richardson
2013-05-07 16:30         ` Greg White
2013-05-07 19:56           ` Wes Felter [this message]
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                   ` [Cerowrt-devel] [Codel] " 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/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='kmbm8e$1a7$1@ger.gmane.org' \
    --to=wmf@felter.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --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