All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ratel <ratel@post.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] class exceeds its ceil
Date: Tue, 27 Dec 2005 12:33:44 +0000	[thread overview]
Message-ID: <43B134A8.5000202@post.pl> (raw)

Hi,

I have a setup like this:

   class 1:1 rate 7600kbit  (on a imq device)
        |
        |\class 1:10 rate 100kbit ceil 5600kbit prio 7 (here goes p2p 
traffic)
         \class 1:12 rate 7500kbit ceil 7600kbit
            |
            |\class 1:121 rate 3100 ceil 7500kbit prio 0
            |\class 1:122 rate 2200 ceil 7500kbit prio 2
             \class 1:123 rate 2200 ceil 7500kbit prio 3 (default)

My problem is: the 1:10 class consumes the whole bandwidth.
This is caused by a massive p2p traffic. I've read similar posts on this 
list, and I can't use the solution proposed by Stef Coene here:  
http://mailman.ds9a.nl/pipermail/lartc/2002q2/003958.html. I match p2p 
packets with both ipp2p and layer7 filters and mark them with iptables 
MARK. I can easily block p2p traffic, but when I allow it - it exceeds 
its ceil and reaches the rate of my internet link, which is unacceptable.
I need to allow other classes to borrow bandwidth from a p2p class, but 
I do not want to allow a p2p class to borrow bandwidth from other 
classes. Is there a way to achieve it ? maybe I should redesign 
something in the above diagram.

W

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-12-27 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 12:33 Ratel [this message]
2005-12-27 12:57 ` [LARTC] class exceeds its ceil Andreas Klauer
2005-12-27 14:27 ` Jody Shumaker
2005-12-27 17:08 ` Ratel
2005-12-27 22:34 ` Jody Shumaker
2005-12-27 23:03 ` Andreas Klauer

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=43B134A8.5000202@post.pl \
    --to=ratel@post.pl \
    --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.