All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RED vs. Tail Drop and docs
Date: Fri, 07 Dec 2001 17:52:39 +0000	[thread overview]
Message-ID: <marc-lartc-100774762516940@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100774430903222@msgid-missing>

On Fri, Dec 07, 2001 at 12:08:25PM -0500, Gregory Maxwell wrote:

Greg, good to see that ou are still alive :-) 

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

You need to own the queue to shape it, yes, and in order to make this
happen, your linux box must be the slowest device in the chain.

This is why I am thinking of the 'stack' qdisc which would work like this:


     ___ 10:___
    /  /    \  \
   /   |    |   \
10:1 10:2 10:3 10:4
   <-   <-   <-
 
Enqueue()s always happen at the highest class, 10:4 in this case, dequeue()s
happen via 10:1, 10:2, 10:3 and 10:4. This would allow you to 'stack' RED,
SFQ and TBF, for example.

Haven't worked out how this would work in the kernel though. The question is
if we should 'push' or 'pull' - should a dequeue first always try to dequeue
10:4 to 10:3, and then from 10:3 to 10:2 etc etc.

What I really miss by the way is a way to poll devices for their queue
length, so 'downstream' devices would be able to own the queue so to speak.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
Trilab                                 The Technology People
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

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

      parent reply	other threads:[~2001-12-07 17:52 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
2001-12-07 17:52 ` bert hubert [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=marc-lartc-100774762516940@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.