From: David McNab <david@rebirthing.co.nz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Specific question on ingress policing
Date: Sun, 14 Mar 2004 04:11:54 +0000 [thread overview]
Message-ID: <4053DB8A.5000805@rebirthing.co.nz> (raw)
In-Reply-To: <4053C9BB.4050209@rebirthing.co.nz>
Roy wrote:
> As I observed, setting 'rate 32kbit index 20' for each will not do anything
> good,
> they were behaving like independent clasess, so total trafic was sum of all
> rates.
> then I reduced rates for all clases su that sum of the rates was max rate
> alocated for that poll
> and it worked more or less.
That's a good approach. I can easily change pyshaper (mentioned in
earlier post) so that once it determines the number of connections
matching a criterion, it divides the bandwidth allocation by the number
of such connections, and generates tc ingress policing filter commands
accordingly.
> I am not sure if this was correct.
>
> probably the best way to find how index works is to look at source code.
I'm very time-constrained. Given that I'm often having to study source
code just to find out how to use other programs, I don't have the time
to do this with tc, sadly. When someone writes a thorougly detailed
manual on tc usage (including a complete tc-filters manpage), it'll be a
good thing.
> class www policer rate 100kbit index 20
> class p2p policer index 20 drop
Can you please provide all your *complete* tc commands, so I can see
this in context and form an understanding?
> more or less it was working
Good to know.
--
Kind regards
David
--
leave this line intact so your email gets through my junk mail filter
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-03-14 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 2:55 [LARTC] Specific question on ingress policing David McNab
2004-03-14 3:32 ` Roy
2004-03-14 4:11 ` David McNab [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=4053DB8A.5000805@rebirthing.co.nz \
--to=david@rebirthing.co.nz \
--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.