All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aron Brand" <Aron@sofaware.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Ingress Shaping  using IMQ
Date: Mon, 19 Jan 2004 13:19:08 +0000	[thread overview]
Message-ID: <50F73B338A7FD943B7937BBCF99BFBDE2DB8BC@mail.sofaware.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]

Hi Guys,

Here is a question that is probably of concern to many of us.

I am under pressure to provide some solution for ingress traffic
shaping. What my customer demands is to divide the downstream (ingress)
of an ADSL lines to two classes of traffic - important traffic and non
important downloads. He has a very reasonable requirement: he wants a
guarantee of at least 1000kbps at all times for the important traffic on
the downstream. 

Using ingress policing would be the trivial solution. But no says the
customer - when the important traffic is not fully utilizing its rate, I
want it to share the excess with other classes. 
After looking around, the answer I found was to use imq, which claims to
allow traffic shaping on ingress traffic. So far so good.

And now I arrive to the question: It is possible to configure everything
in THEORY. The question is, it it really possible for me to give the
guarantee that my customer is asking for? I can think of examples why it
seems that the answer is no. For example, lets say the ingress line is
completely saturated with non-important traffic. How on earth can the
poor HTB determine whether important traffic is being drowned out - or
there is simply no important traffic?
My speculation so far - it is possible to configure these rules, and
indeed this is what IMQ was invented for, but in true life there is no
solution that works - since it is inherently impossible!

Has anyone really created and tested a working ingress traffic shaping
solution?

Aron



[-- Attachment #2: Type: text/html, Size: 2541 bytes --]

             reply	other threads:[~2004-01-19 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 13:19 Aron Brand [this message]
2004-01-19 18:27 ` [LARTC] Ingress Shaping using IMQ Stef Coene
2004-01-20 14:05 ` Aron Brand
2004-01-20 17:45 ` Stef Coene
  -- strict thread matches above, loose matches on Subject: below --
2004-06-24 17:39 [LARTC] Ingress shaping " Fernando.SCamargo

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=50F73B338A7FD943B7937BBCF99BFBDE2DB8BC@mail.sofaware.com \
    --to=aron@sofaware.com \
    --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.