[Top] [All Lists]

Re: [PATCH 2.6] update to network emulation QOS scheduler

To: hadi@xxxxxxxxxx
Subject: Re: [PATCH 2.6] update to network emulation QOS scheduler
From: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Wed, 7 Jul 2004 14:22:16 -0700
Cc: "David S. Miller" <davem@xxxxxxxxxx>, Catalin BOIE <util@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, lartc@xxxxxxxxxxxxxxx
In-reply-to: <1089234699.1026.448.camel@xxxxxxxxxxxxxxxx>
Organization: Open Source Development Lab
References: <20040701113312.43cfe6c5@xxxxxxxxxxxxxxxxxxxxx> <20040702134437.5891e998@xxxxxxxxxxxxxxxxxxxxx> <1088824432.1043.271.camel@xxxxxxxxxxxxxxxx> <20040707111055.32ebb25b@xxxxxxxxxxxxxxxxxxxxx> <1089226667.1027.411.camel@xxxxxxxxxxxxxxxx> <20040707135831.4c98dd51@xxxxxxxxxxxxxxxxxxxxx> <1089234699.1026.448.camel@xxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On 07 Jul 2004 17:11:39 -0400
jamal <hadi@xxxxxxxxxx> wrote:

> On Wed, 2004-07-07 at 16:58, Stephen Hemminger wrote:
> > TBF works but since the sender (on the same local machine) may go over 
> > it's allocation, it will drop packets.
> As should any queue that gets congested.

> > For example, if I use tbf to simulate a slow 33k bits/sec link then 
> > TCP test never
> > completes, it just hangs!  TBF does work for intermediate sizes.
> > 
> > But if I use the pacing simulation it works.
> I am not sure i follow; is this because of the return code from the
> enqueue?

Actually, the problem only occurs if burst is set large (like 2mb).
I think it gets stuck waiting for that much data.

<Prev in Thread] Current Thread [Next in Thread>