CoDel AQM discussions
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: codel@lists.bufferbloat.net, divyasingla1989@gmail.com
Subject: Re: [Codel] About Packet Drop in Codel
Date: Mon, 02 Mar 2015 10:10:42 -0800	[thread overview]
Message-ID: <54F4A7A2.2030009@hp.com> (raw)
In-Reply-To: <CAONkte8SoCJysWWotpf-v4OPtUo4bJ_+TodaNFW8=6mnUDHaTg@mail.gmail.com>

On 03/02/2015 09:43 AM, divya singla wrote:
> please explain me this also:
>
> how codel controls the delay like it drops the packet when it spends
> more time than target and after that it will be retransmitted.
> So in case of retransmission and all, i think delay should be more.
> isn't it?

At the risk of typing beyond my understanding...

CoDel is expected to be deployed in situations where the maximum 
possible queuing is rather large at a bottleneck link.  Probably several 
multiples of the RTT in time/size.  It is a response to a belief that 
throwing more and more memory at queues and holding that every packet is 
sacred is a good thing.  Consider what would/could happen with such 
queues without CoDel and what that would mean to delay.

> Next , How  does UDP react like tcp adjusts its rate when there is
> packet loss and UDP?

UDP doesn't.  The *application* using UDP is expected too, just as 
applications using UDP have been expected to do "the right things" from 
the beginning.

rick jones

>
> On Fri, Feb 27, 2015 at 4:44 AM, Stephen Hemminger
> <stephen@networkplumber.org <mailto:stephen@networkplumber.org>> wrote:
>
>     On Thu, 26 Feb 2015 19:32:58 +0100
>     "Richard Scheffenegger" <rscheff@gmx.at <mailto:rscheff@gmx.at>> wrote:
>
>     > Hi Members,
>     > i am doing M.tech and my research topic is AQM.
>     > i tried to run codel with ns-2.35.
>     > And i found packet loss is more in codel as compared to RED.
>
>     More packet loss is no necessarily a bad thing.
>     You need to measure throughput and latency together.
>
>
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>


  reply	other threads:[~2015-03-02 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 17:12 divya singla
2015-02-26 18:32 ` Richard Scheffenegger
2015-02-26 23:14   ` Stephen Hemminger
2015-03-02 17:43     ` divya singla
2015-03-02 18:10       ` Rick Jones [this message]
2015-03-02 18:22       ` Jonathan Morton
2015-03-02 18:43         ` divya singla
2015-03-02 19:07           ` Jonathan Morton
2015-03-03 18:12             ` divya singla
2015-03-03 18:27               ` Rick Jones
2015-03-02 18:35       ` Jonathan Morton
     [not found] <mailman.153549.1425025588.1815.codel@lists.bufferbloat.net>
2015-02-28  1:57 ` David Collier-Brown

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=54F4A7A2.2030009@hp.com \
    --to=rick.jones2@hp.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=divyasingla1989@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