From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: txqueuelen has wrong units; should be time Date: Wed, 02 Mar 2011 17:50:44 +0100 Message-ID: <1299084644.2920.24.camel@edumazet-laptop> References: <1298793252.8726.45.camel@edumazet-laptop> <20110227125540.40754c5y78j9u2m8@hayate.sektori.org> <20110301222531.24832a93@nehalam> <20110301230754.5ef4ab35@nehalam> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Stephen Hemminger , John Heffner , Bill Sommerfeld , Hagen Paul Pfeifer , Albert Cahalan , Jussi Kivilinna , linux-kernel , netdev@vger.kernel.org To: Mikael Abrahamsson Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Le mercredi 02 mars 2011 =C3=A0 17:41 +0100, Mikael Abrahamsson a =C3=A9= crit : > On Tue, 1 Mar 2011, Stephen Hemminger wrote: >=20 > > Also WRED is not default on faster links because it can't be done f= ast=20 > > enough. >=20 > Before this propagates as some kind of truth. Cisco modern core route= rs=20 > have no problems doing WRED at wirespeed, the above statement is not = true. >=20 looking at cisco docs you provided ( ) , it seems the WRED time limits (instead of bytes/packets limits) are internaly converted to bytes/packets limits quote :=20 When the queue limit threshold is specified in milliseconds, the number of milliseconds is internally converted to bytes using the bandwidth available for the class.=20 So it seems its only a facility provided, and queues are still managed with bytes/packets limits... WRED is able to prob drop a packet when this packet is enqueued. At tim= e of enqueue, we dont know yet the time of dequeue, unless bandwidth is known.