From: "Mindaugas Riauba" <mind@bi.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with HTB shaping
Date: Fri, 12 Dec 2003 14:06:13 +0000 [thread overview]
Message-ID: <marc-lartc-107123880021463@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107096971302455@msgid-missing>
> Depends WHAT do you want to know. All should be correct but
> each shows different things.
I want to know number of bytes sent by specific customer.
Customer corresponds to SFQ leaf.
> In bridging scenario there may be other issues (I didn't
> tested it).
> Counter on upper qdisc shows packets received and leaf
> counts when transmitting.
> ifconfig counts reallu send packets - it may be smaller
> if NIC can't send packet (error).
> If you think there is bug then test with routing setup first,
> I have no time to test with bridge.
Tested with routed setup - the same problem. When there are
only TCP or only UDP data streams everything wents fine. But if
I use one TCP and one UDP stream - counters start to differ.
If I add 3rd TCP stream - difference between ifconfig and tc
counters increases. If 3rd stream is UDP - difference decreases.
If you think that taht could help - I think I can provide root access to
this
box.
Mindaugas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-12-12 14:06 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
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 [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-107123880021463@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.