CoDel AQM discussions
 help / color / mirror / Atom feed
From: Alessandro Bolletta <alessandro@mediaspot.net>
To: "Codel@lists.bufferbloat.net" <Codel@lists.bufferbloat.net>
Subject: [Codel] R:  Using fq_codel queuing on backbone routers
Date: Thu, 3 Jan 2013 18:35:27 +0000	[thread overview]
Message-ID: <F52F175DFC537F48A43937B50B44BCA276D16E2F@EXCHANGE.mediaspot.local> (raw)
In-Reply-To: <1357235866.21409.25372.camel@edumazet-glaptop>

>>On Thu, 2013-01-03 at 17:49 +0000, Alessandro Bolletta wrote:
>> Hi everybody,
> 
>> I read in the main wiki page that CoDel doesn’t work as it should on 
> heavy loaded environments as, for example, backbone routers, right?
> 
>> Well, we’d like to make some test on our core mesh-to-fiber gateway 
>> when we’ll get our fiber connection but it isn’t too much clear what 
>> did you mean in wiki.
> 
>  
> 
>> For example: do you think that fq_codel will be able to manage 
>> thousands flows correctly on core router connected to a 1Gbit 
>> symmetric fiber link?

>Of course it will be able to manage this workload on current hardware.

>It adds a small overhead compared to a mere fifo. I guess you already use a complex qdisc hierarchy anyway, so you'll >hardly notice a performance impact at all.

I'd like to guarantee "net neutrality" for my customers as much as possible (I'm thinking to priorize only SIP/RTP UDP traffic), so I prefer to preserve qdisc hierarchy much simpler than other ISPs' queues.

CoDel should help to keep my mesh traffic (internal and external) away from bufferbloat in case of traffic congestion on my fiber gateway.

      reply	other threads:[~2013-01-03 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 17:49 [Codel] " Alessandro Bolletta
2013-01-03 17:57 ` Eric Dumazet
2013-01-03 18:35   ` Alessandro Bolletta [this message]

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=F52F175DFC537F48A43937B50B44BCA276D16E2F@EXCHANGE.mediaspot.local \
    --to=alessandro@mediaspot.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