From: Greg Stark <gsstark@mit.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit?
Date: Wed, 09 Jun 2004 00:26:41 +0000 [thread overview]
Message-ID: <87wu2hwp8e.fsf@stark.xeocode.com> (raw)
Damion de Soto <damion@snapgear.com> writes:
> You can create different ingress policers that only match specific ports, and
> give them different priorities, but that still won't work as well as using IMQ,
> or if your box is a gateway (and you are only shaping traffic going through it),
> then you can use egress queues on the LAN interface.
For some reason that hadn't occurred to me. That should work just fine. I
guess I should mark the packets in iptables to avoid throttling traffic from
gateway itself, or does match see the external ip?
IMQ does seem like a handy tool, but why is there a distinction at all between
egress and ingress qdiscs at all? Why not just allow people to attach HTB as
an ingress qdisc directly?
I suppose in an ideal world the best thing would be to receive the packets,
hand them to user-space, but not mark them as received, ie, not ack them. That
avoids introducing any loss from the user point of view but still slows the
flow down. But that seems fiddly and would only work for TCP I guess.
--
greg
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-06-09 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 0:26 Greg Stark [this message]
2004-06-09 0:52 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit? Damion de Soto
2004-06-09 3:33 ` Greg Stark
2004-06-09 4:01 ` Jason Boxman
2004-06-09 8:47 ` Greg Stark
2004-06-09 19:46 ` [LARTC] Re: how flexible is ingress traffic policing to Sanjay Arora
2004-06-09 20:09 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit? Greg Stark
2004-06-09 21:06 ` Jason Boxman
2004-06-11 0:17 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth 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=87wu2hwp8e.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--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.