Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Question on TC filter
Date: Sat, 11 Jan 2003 10:54:48 +0000	[thread overview]
Message-ID: <marc-lartc-104228252522155@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104222313403706@msgid-missing>

On Saturday 11 January 2003 05:57, Cheng Kwok Wing, William wrote:
> Thanks for your reply. I've visited your web
> http://home.docum.org/qos/ already. I just wonder if
> there are some better ways to add and remove class one
> by one rather than writing the script all the time.
>
> In addition, each time your run the tc script. You
> need to remove the root qdisc, i.e. clear all setting,
> first. Then, all counters are reset......... How to
> solve such problem if I want to dump the data from "tc
> -s -d class dev eth1" and plot graph using rrdtools
> (without losing previous data)??
rrdtool is smart enough to understand what happens.  It stores the difference 
between 2 updates and a negative update is not possible.  So that update is 
ignored.  But that's hardly visible on a graph.
So restting the counters is no problem if you use rrdtool to store the data.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

      parent reply	other threads:[~2003-01-11 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 18:24 [LARTC] Question on TC filter Cheng Kwok Wing, William
2003-01-10 23:00 ` Stef Coene
2003-01-11  4:54 ` Cheng Kwok Wing, William
2003-01-11  4:57 ` Cheng Kwok Wing, William
2003-01-11 10:54 ` Stef Coene [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-104228252522155@msgid-missing \
    --to=stef.coene@docum.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox