netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* RED + ECN not working
@ 2007-01-09 16:08 rbj2
  2007-01-15  8:38 ` Jarek Poplawski
  0 siblings, 1 reply; 2+ messages in thread
From: rbj2 @ 2007-01-09 16:08 UTC (permalink / raw)
  To: netdev; +Cc: rbj2

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.

Thanks,
Rahul.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RED + ECN not working
  2007-01-09 16:08 RED + ECN not working rbj2
@ 2007-01-15  8:38 ` Jarek Poplawski
  0 siblings, 0 replies; 2+ messages in thread
From: Jarek Poplawski @ 2007-01-15  8:38 UTC (permalink / raw)
  To: rbj2; +Cc: netdev

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-01-15  8:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-01-09 16:08 RED + ECN not working rbj2
2007-01-15  8:38 ` Jarek Poplawski

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).