All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Slinn <mslinn@zamples.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Resetting traffic history
Date: Thu, 21 Oct 2004 23:13:36 +0000	[thread overview]
Message-ID: <417842A0.8030002@zamples.com> (raw)
In-Reply-To: <416D89ED.6090508@zamples.com>

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

I'm a tc newbie, and I think I am close to being able to use it to 
control one of the virtual web sites on our Gentoo Linux server.  The 
site has it's own IP address.  I have a bit of a problem in that the way 
I originally configured tc, the busy site grabbed all the bandwidth, 
leaving none for the other (and more important) sites.  Here is how I 
had configured it:

    tc qdisc replace dev $NIC root tbf rate $RATE_TOTAL latency 50ms
    burst $BURST

The total data rate was pegged within acceptable limits, but the problem 
is that data stopped flowing after tc was active after a few hours.  The 
busy site had a few peak periods and presumably used up all the traffic 
allotment.  Perhaps tc remembers the traffic between invocations?

I then tried a slightly more sophisticated setup:

    tc qdisc del dev $DEV root
    tc qdisc  add dev $NIC root handle 1: cbq avpkt 1000 bandwidth 1000mbit
    tc class  add dev $NIC parent 1: classid 1:1 cbq rate $RATE_PROBLEM
    allot 1500 prio 5 bounded # isolated
    tc filter add dev $NIC parent 1: protocol ip prio 16 u32 match ip
    dst $IP flowid 1:1

Unfortunately, I still don't get any traffic flowing while tc is active 
now.  Seems that I need to reset something.  Any suggestions?  I've shut 
down the problem site and disabled tc while I try to figure out a solution.

Thanks for your help!

Mike
mslinn at mslinn.com

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

      parent reply	other threads:[~2004-10-21 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 20:02 [LARTC] Resetting traffic history Mike Slinn
2004-10-13 23:27 ` Andy Furniss
2004-10-21 23:13 ` Michael Slinn [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=417842A0.8030002@zamples.com \
    --to=mslinn@zamples.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.