CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dong Mo <montedong@gmail.com>
To: Anirudh Sivaraman <sk.anirudh@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] How to make a bufferbloat fairqueue with tc qdisc
Date: Thu, 5 Dec 2013 14:45:29 -0600	[thread overview]
Message-ID: <CAAUsAoRd8R5FxXk=t183zuUtmkT59cbLOdhJNQkhuqz_nPcr9g@mail.gmail.com> (raw)
In-Reply-To: <CAMdC6xb4iyaL=hBZjspVP3YsZ6d2sxYZ-OrTXFRr3Tg_Fr2NwA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

Thanks. I made a wrong observation for the last email that I used ping to
measure the latency of TCP and was expecting to see a latency explode.

So do you know a way to measure the running TCP's packet latency
experienced at the qdisc?
Thanks a lot
-Mo




2013/12/5 Anirudh Sivaraman <sk.anirudh@gmail.com>

> On Thu, Dec 5, 2013 at 2:52 PM, Dong Mo <montedong@gmail.com> wrote:
> > Dear List,
> > I am trying to make a bufferbloat fairqueue with qdisc and compare that
> with
> > fq_codel.
> > However, I am now having some hard time doing it.
> >
> > The commands I am using are:
> >
> > tc qdisc add dev $IFACE root handle 1: htb default 1
> > tc class add dev $IFACE parent 1: classid 1:1 htb rate 40mbit
> > tc qdisc del dev eth4 parent 1:1 handle 10: sfq perturb 10
> >
> > And sending packet from the sender, where sfq qdisc is set, to the
> receiver,
> > the queuing delay is quite small and is approximately the same as when
> > fq_codel enabled.
> >
> > However, if I am not using sfq (only htb set), and send only one flow
> over
> > this link, the delay will explode again.
> >
> > So is sfq here cut off the queue length somehow? How should I make a
> > bufferbloat fair queue on linux box using tc qdisc?
> >
>
> You could start with the fq_codel qdisc and set the codel interval and
> target parameters to absurdly large values (say 1000 seconds each) to
> simulate a qdisc that has fair queuing but almost never drops a
> packet.
>
> Anirudh
>
> > Thanks
> >
> > -Mo Dong
> >
> > _______________________________________________
> > Codel mailing list
> > Codel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/codel
> >
>

[-- Attachment #2: Type: text/html, Size: 2457 bytes --]

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 19:52 Dong Mo
2013-12-05 20:36 ` Anirudh Sivaraman
2013-12-05 20:45   ` Dong Mo [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='CAAUsAoRd8R5FxXk=t183zuUtmkT59cbLOdhJNQkhuqz_nPcr9g@mail.gmail.com' \
    --to=montedong@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=sk.anirudh@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