From: David McNab <david@rebirthing.co.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] Weird quirk with ingress policing
Date: Sun, 14 Mar 2004 11:11:13 +0000 [thread overview]
Message-ID: <40543DD1.5020702@rebirthing.co.nz> (raw)
Hi,
I notice that if two or more existing connections match an ingress
policing filter, the input bandwidth does not get evenly divided up
between the n connections.
Kinda like litters of baby animals, where the stronger babies get more
access to the mothers teats and grow up bigger and faster than their
siblings.
The only workaround that's working for me is to set explicit ingress
policing filters, which match src and dest host and port, so for each
filter there can only be exactly one connection which matches. Then,
it's just a matter of evenly dividing up the allocated total input bw
amongst these n processes. This works, but it's not exactly optimal.
--
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/
next reply other threads:[~2004-03-14 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 11:11 David McNab [this message]
2004-03-14 18:33 ` [LARTC] Weird quirk with ingress policing Roy
2004-03-14 22:51 ` David McNab
2004-03-16 0:34 ` Andy Furniss
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=40543DD1.5020702@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox