Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Greg White <g.white@CableLabs.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>,
	Jonathan Morton <chromatix99@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Codel] [Bloat] Latest codel, fq_codel, and pie sim study from cablelabs now available
Date: Tue, 7 May 2013 16:22:23 +0000	[thread overview]
Message-ID: <CDAE85E3.1191F%g.white@cablelabs.com> (raw)
In-Reply-To: <20130506224732.1795f13a@redhat.com>

BTW, the SFQ-CoDel code does support the "new" flows concept in much the
same way as the linux code, so this was already included in the simulation
results. 



On 5/6/13 2:47 PM, "Jesper Dangaard Brouer" <jbrouer@redhat.com> wrote:

>On Mon, 6 May 2013 21:46:35 +0300 Jonathan Morton
><chromatix99@gmail.com> wrote:
>> On 6 May, 2013, at 8:54 pm, Jesper Dangaard Brouer wrote:
>> 
>> > A flow is considered "new" if no packets for the given flow exists
>> > in the queue.  It does not have to be a truly new-flow, it just
>> > have to send packets "slow"/paced enough, that the queue is empty
>> > when the next packet arrive.
>> > 
>> > Perhaps VoIP would fit this traffic profile, and thus would work
>> > better with the Linux fq_codel implementation, compared to the
>> > SFQ-Codel used in the simulation.
>> 
>> That doesn't work, because the with a sufficient number of BT flows,
>> the flow queue containing the VoIP flow is the fullest queue, not the
>> emptiest.  That's independent of the number of flow queues, including
>> the infinite case.  Think about it carefully.
>
>Yes, I agree.
>
>And as I mentioned, with the fq_codel implementation details, this is
>going to hit even earlier, as we have a limited number of flow/hash
>queues.
>
>> Looking at the implementation, it does have the problem that the match
>> for "if the flow already have packets in the queue" just looks to see
>> if the hash bucket is empty.  Thus 2 stream sharing a hash queue throw
>> this off.
>
>--
>Best regards,
>  Jesper Dangaard Brouer
>  MSc.CS, Sr. Network Kernel Developer at Red Hat
>  Author of http://www.iptv-analyzer.org
>  LinkedIn: http://www.linkedin.com/in/brouer
>_______________________________________________
>Codel mailing list
>Codel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/codel


  reply	other threads:[~2013-05-07 16:22 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 [this message]
2013-05-07 13:31       ` [Cerowrt-devel] " Michael Richardson
2013-05-07 16:30         ` Greg White
2013-05-07 19:56           ` 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                   ` [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=CDAE85E3.1191F%g.white@cablelabs.com \
    --to=g.white@cablelabs.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=jbrouer@redhat.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