From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Specific question on ingress policing
Date: Sun, 14 Mar 2004 03:32:14 +0000 [thread overview]
Message-ID: <001201c40974$f237b550$030aa8c0@t> (raw)
In-Reply-To: <4053C9BB.4050209@rebirthing.co.nz>
One remark: policers have nothing to do with incoming bandwitch they also
can be used with any forwarded trafic,
(if you will make attempt to use them on localy originated packets you can
even hang your computer)
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.
I am not sure if this was correct.
probably the best way to find how index works is to look at source code.
It can be very usefull feature. Which could alow do this:
if www trafic rate exceeds 100kb/s then drop all p2p packets
I was trying this in such way
class www policer rate 100kbit index 20
class p2p policer index 20 drop
more or less it was working
----- Original Message -----
From: "David McNab" <david@rebirthing.co.nz>
To: <>
Sent: Sunday, March 14, 2004 4:55 AM
Subject: [LARTC] Specific question on ingress policing
> Hi,
>
> After more research, and a couple of kind replies to earlier questions,
> I've tried putting 'index nnn' in my ingress policers.
>
> It appears that connections matching ingress policers with (say) 'rate
> 32kbit index 20' share a total incoming bandwidth pool of 32kbits.
>
> Is that indeed the case?
>
> In other words - if I have one ingress policer that matches 3 current
> connections, and another ingress policer matching 2 current connections,
> and both policers are set to 'rate 32kbit index 20' - is it true that
> inbound bandwidth for all 5 connections is throttled to a shared total
> of 32kbit?
>
> Thanks and 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/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-14 3:32 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 [this message]
2004-03-14 4:11 ` David McNab
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='001201c40974$f237b550$030aa8c0@t' \
--to=roy@xxx.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.