From: "Mindaugas Riauba" <mind@bi.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with HTB shaping
Date: Thu, 11 Dec 2003 06:52:18 +0000 [thread overview]
Message-ID: <marc-lartc-107112631404402@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107096971302455@msgid-missing>
> > I have some strange problems with shaping. Now I'm testing Linux as
> > shaping bridge. Redhat Linux 7.3, kernel plain 2.4.23 with latest HTB
patch
> > from devik and PSCHED_CLOCK_SOURCE changed to PSCHED_CPU.
> > What I'm doing wrong?
> I'm not sure, but I think that the network statistics are counting every
bit
> that's been put on the wire. And maybe this also includes retransmits.
OK. I did few more tests and got following results for transmited bytes.
Interface is shaped at 512kbps, tests run for 100 seconds.
- tc class reports 5910888 bytes (~432kbps)
- ifconfig eth1 reports 6704130 bytes (~523kbps)
- tc rate reports rate 66140bps (6614000 bytes, 516kbps)
As you see difference is quite essential.
But if I count packets:
- tc class reports 15444 packets
- ifconfig eth1 reports 15504 packets
Results are practically the same.
Could it be that HTB somewhere does not update bytes statistics?
Mindaugas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-11 6:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 11:24 [LARTC] Problems with HTB shaping Mindaugas Riauba
2003-12-09 20:11 ` Stef Coene
2003-12-10 5:49 ` Mindaugas Riauba
2003-12-11 6:52 ` Mindaugas Riauba [this message]
2003-12-11 9:44 ` devik
2003-12-11 11:51 ` Mindaugas Riauba
2003-12-11 14:04 ` devik
2003-12-11 14:10 ` Mindaugas Riauba
2003-12-11 14:19 ` devik
2003-12-11 18:49 ` Kabelweb
2003-12-12 14:06 ` Mindaugas Riauba
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-107112631404402@msgid-missing \
--to=mind@bi.lt \
--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.