From: John Default <default@advaita.sytes.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Token Bucket Filter and Dropping
Date: Wed, 09 May 2007 20:24:22 +0000 [thread overview]
Message-ID: <46422DF6.7000405@advaita.sytes.net> (raw)
In-Reply-To: <002a01c79166$3e53a7b0$bafaf710$@pl>
Hi
No need for htb, simple tbf will do.
But if you are creating your own:
As i understand token bucket, you should take each packet from the end
of queue in order they are there, i.e S1, S2, S1, S2, not just each
other. When the bucket is full, you will drop every packet on input. It
is unlikely that you will free space in buffer everytime right when S2
packet comes... You would have buffer full of s2 then, not s1|s2|s1...
as you say. Are you sure you are dequeuing from front and doing tail-drop ?
As i understand:
dequeue at constant
rate<--que_front_s1,s2,s1,s2,s1,s2_que_tail<--enqueue input or drop
Maybe change in size of token could help mix this... How big is one
token now? (i do not know how your tbf is implemented...)Can you give
more details ?
By the way: how are you creating those streams, i think it is unusual to
see such properly ordered packets of streams in real life ...
If i am completely out, sorry then, just beginner.
Best regards (default)
Piotr Wójcicki wrote:
> I am trying to create my own Token Bucket Filter. However, I have a problem
> with packet dropping.
>
> Scenario :
> I got two streams 20KB/s each.
> I got one bucket with rate 20KB/s
>
> I put both streams into this bucket.
>
> When buffer is full packets need to be dropped. The problem is that only
> every other packet needs to be dropped in this scenario.
> Streams are the same so queue looks like that :
>
> S1 | S2 | S1 | S2
>
> Packets form both streams are one by one.
> The result is that all packets from stream S1 are being dropped and all
> packets from Stream S2 are being sent.
> Ideally half of dropped packets would be from S1 and half from S1.
>
> What are possible solutions to this problem ?
>
>
> Piotr Wojcicki
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-05-09 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 11:44 [LARTC] Token Bucket Filter and Dropping Piotr Wójcicki
2007-05-08 14:03 ` Marco Aurelio
2007-05-08 15:08 ` Piotr Wójcicki
2007-05-09 20:24 ` John Default [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=46422DF6.7000405@advaita.sytes.net \
--to=default@advaita.sytes.net \
--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.