CoDel AQM discussions
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: divya singla <divyasingla1989@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] About Packet Drop in Codel
Date: Tue, 03 Mar 2015 10:27:33 -0800	[thread overview]
Message-ID: <54F5FD15.1030605@hp.com> (raw)
In-Reply-To: <CAONkte8VwBrVAgwTb=tfQCwPYqXOjjmtOKBVEbzpU=0J00QS_Q@mail.gmail.com>

On 03/03/2015 10:12 AM, divya singla wrote:
> But Sir i heard that UDP does not respond to congestion.Even though its
> packets are lost, it keeps sending packets at the same rate(unlike tcp)

UDP does not and never has.  All it has ever done is send what the 
application has told it to send as the application tells it to. The 
*application* using UDP is expected to respond to congestion.

rick jones

>
> -- please answer this too:
>   Does codel implement concept of marking(ECN)  in ns2?
>
>
> On Tue, Mar 3, 2015 at 12:37 AM, Jonathan Morton <chromatix99@gmail.com
> <mailto:chromatix99@gmail.com>> wrote:
>
>     With UDP, you're at the mercy of the application using it. With TCP,
>     you're merely at the mercy of the operating system.
>
>     AQM acts on UDP packets in the same way as TCP packets - in fact it
>     can't tell them apart. So any application which detects and responds
>     to UDP packet loss in the same way as TCP does, will back off just
>     the same.
>
>     In practice, UDP is used for several different types of application:
>
>     - simple request response, such as DNS and NTP, where eliminating
>     TCP's connection setup overhead is important. In any case, TCP's
>     congestion control doesn't get a chance to do any good on such s
>     short-lived connection. Packet loss in this situation is tolerated
>     by retry, with exponential backoff as an alternative congestion
>     control measure.
>
>     - latency sensitive and often isochronous (inelastic) flows like
>     VoIP. Packet loss may lead to a loss of quality, but there is little
>     the application can do to reduce its loss except dropping the call
>     completely.
>
>     - as a way to implement delay sensitive and pacific congestion
>     control algorithms, as in uTP.
>
>     A flow isolation system, such as that in fq_codel, will often leave
>     UDP flows alone completely, because they tend not to be the ones
>     using the bulk of the bandwidth. Conversely, if a single UDP flow
>     was responsible for the congestion, it would let the other traffic
>     bypass it. This is why fq_codel is better than just plain codel, if
>     you can get it.
>
>     - Jonathan Morton
>
>
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>


  reply	other threads:[~2015-03-03 18:27 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
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 [this message]
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=54F5FD15.1030605@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