From: Jarek Poplawski <jarkao2@o2.pl>
To: rbj2@njit.edu
Cc: netdev@vger.kernel.org
Subject: Re: RED + ECN not working
Date: Mon, 15 Jan 2007 09:38:48 +0100 [thread overview]
Message-ID: <20070115083848.GA1644@ff.dom.local> (raw)
In-Reply-To: <1168358884.45a3bde4a14b9@webmail.njit.edu>
On 09-01-2007 17:08, rbj2@njit.edu wrote:
> Hello,
>
> I have been trying to get the RED qdisc and ECN to work for the past few weeks
> and all my experiments have failed. Here is the setup I am using.
>
> Src -- R1 -- R2 -- Dst
>
> Between Src and R1 is a 100Mbps link and between R1 and R2 a 10Mbps link. I set up
> the qdisc at R1 as follows
>
> tc qdisc add dev eth3 root handle 1: prio
> tc qdisc add dev eth3 parent 1:1 handle 10: sfq
> tc qdisc add dev eth3 parent 1:2 handle 20: sfq
> tc qdisc add dev eth3 parent 1:3 handle 30: red limit 10000 min 3000 max 5000
> avpkt 1000 burst 5 probability 0.5 bandwidth 256kbit ecn
>
> I also inserted printk statments inside the code to print the calculate queue average (RED param), the
> backlog (Qdisc param) and the queue length (sk_buff_head param). I also inserted print statements for
> each action of RED i.e. DONT_MARK, PROB_MARK, HARD_MARK and DROP.
>
> For the purpose of my experiments, I transferred a 25 MB file. I also did 100 simultaneous TCP
> transfers for 2 mins using ipref. In all cases none of the packets were either marked or dropped by the
> RED code. This was verified by the print statements in the logs. For all runs, qavg and backlog were 0
> and qlen was 1.
>
> I have even tried classless red and got same results. Does anyone know whether RED+ECN work ? Any
> tests and setups that someone has used and got successful results ? I would really appreciate any input
> or suggestions on this.
Hi,
Did you try with lartc.org list?
And probably there could be more details, like:
- where is eth3
- tc -s -d qdisc show dev eth3 (before and after the transfer)
- kernel and iproute versions
Regards,
Jarek P.
prev parent reply other threads:[~2007-01-15 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 16:08 RED + ECN not working rbj2
2007-01-15 8:38 ` Jarek Poplawski [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070115083848.GA1644@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=netdev@vger.kernel.org \
--cc=rbj2@njit.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;
as well as URLs for NNTP newsgroup(s).