All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@linuxpower.cx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RED vs. Tail Drop and docs
Date: Fri, 07 Dec 2001 17:08:25 +0000	[thread overview]
Message-ID: <marc-lartc-100774498106329@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100774430903222@msgid-missing>

On Fri, Dec 07, 2001 at 11:57:34AM -0500, Michael T. Babcock wrote:
> And for those wondering why I'd care to have RED instead of basic
> SFQ (although GRED might handle this as I'd like it to), see:
> 
> http://www.google.com/search?qÊche:3RbzYw9RPU4:www-users.cs.umn.edu/~mhasan/finalpres.ppt+gred+queue&hl=en
> 
> Scroll down to about the 1/3 mark or search 'red vs. tail drop'. Its
> a converted powerpoint presentation (from:
> http://www-users.cs.umn.edu/~mhasan/finalpres.ppt)

Also, try a search on SFB (Blue queue). I started writing a kernel qdisc for
SFB, but never finished, partly because it really needs to be integrated
with a class based system to give the needed flexibility (i.e. if it isn't
you will have to choose between the two) and partly because figuring out how
to correctly hook the 'busyness' of the interface.

A further problem is that Linux based shaper boxes are often not directly
connected to the 'slow link', but instead there is a separate router which is
taking in a much faster interface, performing it's own (often tail drop)
queuing, and pushing out on the slow interface. This configuration is the
biggest contributer to traffic control not behaving as expected.




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-12-07 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 16:57 [LARTC] RED vs. Tail Drop and docs Michael T. Babcock
2001-12-07 17:08 ` Gregory Maxwell [this message]
2001-12-07 17:52 ` bert hubert

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=marc-lartc-100774498106329@msgid-missing \
    --to=greg@linuxpower.cx \
    --cc=lartc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.