From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
John Heffner <johnwheffner@gmail.com>,
Bill Sommerfeld <wsommerfeld@google.com>,
Hagen Paul Pfeifer <hagen@jauu.net>,
Albert Cahalan <acahalan@gmail.com>,
Jussi Kivilinna <jussi.kivilinna@mbnet.fi>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: txqueuelen has wrong units; should be time
Date: Wed, 02 Mar 2011 17:50:44 +0100 [thread overview]
Message-ID: <1299084644.2920.24.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.1103021739550.7942@uplift.swm.pp.se>
Le mercredi 02 mars 2011 à 17:41 +0100, Mikael Abrahamsson a écrit :
> On Tue, 1 Mar 2011, Stephen Hemminger wrote:
>
> > Also WRED is not default on faster links because it can't be done fast
> > enough.
>
> Before this propagates as some kind of truth. Cisco modern core routers
> have no problems doing WRED at wirespeed, the above statement is not true.
>
looking at cisco docs you provided
( <http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/12stbwr.html>
)
, it seems the WRED time limits (instead of bytes/packets limits) are
internaly converted to bytes/packets limits
quote :
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.
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 time
of enqueue, we dont know yet the time of dequeue, unless bandwidth is
known.
prev parent reply other threads:[~2011-03-02 16:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 5:44 txqueuelen has wrong units; should be time Albert Cahalan
2011-02-27 7:02 ` Mikael Abrahamsson
2011-02-27 7:54 ` Eric Dumazet
2011-02-27 8:27 ` Albert Cahalan
2011-02-27 10:55 ` Jussi Kivilinna
2011-02-27 20:07 ` Eric Dumazet
2011-02-27 21:32 ` Jussi Kivilinna
2011-02-28 11:43 ` Jussi Kivilinna
2011-02-28 13:10 ` Eric Dumazet
2011-02-28 18:31 ` Jussi Kivilinna
2011-02-28 16:11 ` John W. Linville
2011-02-28 16:48 ` Eric Dumazet
2011-02-28 16:55 ` John W. Linville
2011-02-28 17:18 ` Eric Dumazet
2011-02-28 21:45 ` John Heffner
2011-03-01 4:11 ` Albert Cahalan
2011-03-01 4:18 ` David Miller
2011-03-01 6:54 ` Albert Cahalan
2011-03-01 7:25 ` David Miller
2011-03-01 7:26 ` Eric Dumazet
2011-03-01 19:37 ` Albert Cahalan
2011-03-01 20:14 ` Eric Dumazet
2011-03-01 20:16 ` Eric Dumazet
2011-03-02 3:10 ` Mikael Abrahamsson
2011-03-02 20:25 ` Chris Friesen
2011-03-01 5:01 ` Eric Dumazet
2011-03-01 5:36 ` Eric Dumazet
2011-02-27 23:33 ` Albert Cahalan
2011-02-28 11:23 ` Jussi Kivilinna
2011-03-02 21:54 ` [RFC LOL OMG] pfifo_lat: qdisc that limits dequeueing based on estimated link latency John W. Linville
2011-03-02 22:08 ` John W. Linville
2011-03-03 12:51 ` Eric Dumazet
2011-02-28 15:38 ` txqueuelen has wrong units; should be time Hagen Paul Pfeifer
2011-02-28 16:37 ` Albert Cahalan
2011-02-28 17:45 ` John W. Linville
2011-02-28 17:20 ` Bill Sommerfeld
2011-02-28 21:51 ` John Heffner
2011-03-01 0:46 ` Mikael Abrahamsson
2011-03-02 6:25 ` Stephen Hemminger
2011-03-02 6:41 ` Mikael Abrahamsson
2011-03-02 7:07 ` Stephen Hemminger
2011-03-02 16:41 ` Mikael Abrahamsson
2011-03-02 16:50 ` Eric Dumazet [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=1299084644.2920.24.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=acahalan@gmail.com \
--cc=hagen@jauu.net \
--cc=johnwheffner@gmail.com \
--cc=jussi.kivilinna@mbnet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=swmike@swm.pp.se \
--cc=wsommerfeld@google.com \
/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