All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Complex Traffic shaping setup
Date: Fri, 18 Feb 2005 13:31:51 +0000	[thread overview]
Message-ID: <3063e50502180531164e16ff@mail.gmail.com> (raw)
In-Reply-To: <4215E636.5070206@inventum.cc>

I'm not sure if you have to use different prio for filters (With fw
this is a must). Depends on your setup.
With htb, everything is attached with parent as root qdisc.


On Fri, 18 Feb 2005 18:27:26 +0530, Padam J Singh
<padam.singh@inventum.cc> wrote:
>  Hi!
>  
>  
>  I have the following setup using iproute2: 
>  
>  ====
>  | Root |
>  ====
>      |
>      |           =======>      ------------| Box Level 1 |
>      |           =======>      |
>      |           =======>      ------------| Box Level 2 |
>      |           =======>      |
>      |
>      |           =======>      ------------|    Users    |
>                  =======>                         | 
>                         |           =======>                         ------------|    User 1   |
>                         |           =======>                         |
>                         |           =======>                         ------------|    User 2   |
>                         |           ======== 
>                         |
>                         |           =======>                         ------------|     User 3  |
>                                     =======>  
>  
>  I am using HTB for each node, simply because it supports burst mode.
>  
>  There are box level classes (top level classes) that might limit bandiwdth
> based on protocols (http, smtp etc)
>  Then there are users classes which rate limit each user to a specific rate.
>  
>  Each Box Level and User Classes have associated Qdiscs as well.
>  
>  The issue is that HTB seems to be rate limiting only if I attach filters at
> the root (1:).
>  
>  Since classification for box level classes may also match more specific
> user filters are well, one of the two things happen:
>  
>  1. If the prio of the filters for Box level is higher or equal than that of
> Users, packets are only sent to the box level class, and since the rate at
> box level class is generally higher, the user starts exceeding his limit.
>  2. If the prio of the User filter is higher, packets matching the user
> filter are never sent to the Box level classes, making the box level rate
> for a particular protocol exceed the required for all users put together.
>  
>  Is there a solutions to this issue? I am unable to really find a solution
> since filters can only be applied to the root!
>  
>  Thanks in advance!
>  Padam Singh.
>  
> 


-- 
Bla bla
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2005-02-18 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 13:09 [LARTC] Complex Traffic shaping setup Padam J Singh
2005-02-18 13:31 ` George Alexandru Dragoi [this message]
2005-02-18 19:42 ` rsenykoff

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=3063e50502180531164e16ff@mail.gmail.com \
    --to=waruiinu@gmail.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.