From: Amogh Vasekar <amoghvk@stanford.edu>
To: codel@lists.bufferbloat.net
Cc: cs244-spr1112-staff@lists.stanford.edu,
Rishita Anubhai <rishita@stanford.edu>
Subject: [Codel] CoDel + 3.3 kernel
Date: Wed, 23 May 2012 15:02:24 -0700 [thread overview]
Message-ID: <CAAAcUj47s+BuusQBuKhBWHys7ZCyMdXhsxc+Yfw6CLHK5n8Zqg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Hello Developers,
This is Amogh here, a Masters student at Stanford University. As a first
step towards exploring CoDel, we're trying to reproduce the results on EC2
using OpenFlow + Mininet and then take it from there.
So far, I have CoDel with kernel 3.3 (Thanks for the deb packages! More on
kernel 3.4 later), with the codel specific iproute2 patch installed.
With htb qdisc at root, and CoDel children I have an output as follows :
---------
tc -s qdisc show dev eth0
qdisc htb 1: root refcnt 2 r2q 10 default 12 direct_packets_stat 770
Sent 112338 bytes 961 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc codel 110: parent 1:11 [Unknown qdisc, optlen=32]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc codel 120: parent 1:12 [Unknown qdisc, optlen=32]
Sent 6364 bytes 56 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc codel 130: parent 1:13 [Unknown qdisc, optlen=32]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
-------------------
I was wondering why I get an Unknown qdisc, optlen=32 error, even after
using the codel-specific iproute2 from Git. I noticed that the Git package
has fq_codel specific code (I am using base Codel in kernel 3.3), is it not
configured to handle this?
Thanks for your help, excited about CoDel !! Let us know if you have any
suggestions.
Amogh
[-- Attachment #2: Type: text/html, Size: 1549 bytes --]
next reply other threads:[~2012-05-23 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 22:02 Amogh Vasekar [this message]
2012-05-23 22:36 ` Dave Taht
2012-05-24 0:00 ` Rishita Rajal Anubhai
2012-05-24 0:19 ` Jonathan Morton
2012-05-24 0:27 ` Dave Taht
2012-05-24 3:01 ` Jonathan Morton
2012-05-26 9:01 ` Rishita Rajal Anubhai
2012-05-26 11:14 ` Roger Jørgensen
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=CAAAcUj47s+BuusQBuKhBWHys7ZCyMdXhsxc+Yfw6CLHK5n8Zqg@mail.gmail.com \
--to=amoghvk@stanford.edu \
--cc=codel@lists.bufferbloat.net \
--cc=cs244-spr1112-staff@lists.stanford.edu \
--cc=rishita@stanford.edu \
/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