From: "Mindaugas Riauba" <mind@bi.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Semi-shaped traffic
Date: Mon, 30 Dec 2002 13:47:45 +0000 [thread overview]
Message-ID: <marc-lartc-104125615011169@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104045399325537@msgid-missing>
> >
> > Well I'd prefer to leave that to professionals :). Who is packet
> > filters maintainer? Alexey Kuznetsov?
>
> Filters ?? If you mean qos classifiers (badly named filters in tc tool)
> then yes, Alexey. If you mean iptables then I'm not sure.
I mean packet schedulers :).
And OK. This problem is avoidable. But as another test I tried to
flood link with two data streams - one UDP, one TCP, both going the same
direction. Then total traffic drops considerably. Data is below.
In bytes. Traffic is shaped to 256kbit.
Two TCP streams or one UDP stream is shaped without problems.
Traffic flows at ~33000
Mindaugas
1 1041255151 1041255161 21100.6 21100.6 21100.6
1 1041255161 1041255171 18968.4 18968.4 18968.4
1 1041255171 1041255181 19081.9 19081.9 19081.9
1 1041255181 1041255191 19946.4 19946.4 19946.4
1 1041255191 1041255201 33362 33362 33362
1 1041255201 1041255211 33105.7 33105.7 33105.7
1 1041255211 1041255221 17019.4 17019.4 17019.4
1 1041255221 1041255231 17146.2 17146.2 17146.2
1 1041255231 1041255241 18635.5 18635.5 18635.5
1 1041255241 1041255251 16486.2 16486.2 16486.2
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-30 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 6:58 [LARTC] Semi-shaped traffic Mindaugas Riauba
2002-12-24 11:48 ` Mindaugas Riauba
2002-12-27 9:12 ` devik
2002-12-27 9:19 ` devik
2002-12-30 8:21 ` Mindaugas Riauba
2002-12-30 10:02 ` devik
2002-12-30 13:47 ` 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-104125615011169@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.