From: Patrick Turley <pturley@rocksteady.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Parameters for the ingress qdisc?
Date: Tue, 05 Aug 2003 20:59:14 +0000 [thread overview]
Message-ID: <marc-lartc-106011742407167@msgid-missing> (raw)
I can't find any documentation on the paramaters for the ingress qdisc.
Can someone help me?
I have a number of filters feeding into my ingress qdisc, all of which
are rate limited, but I want to place a limit on the aggregate flow as
well. I don't want to monitor the sum of the flow rates - I want to
place a hard ceiling on the total possible flow that overrides
everything else.
Any further details about the internal workings of the ingress qdisc
would also be very helpful. I've seen some stuff that suggests its
really a TBF in disguise, but I'm not sure. In particular, I'd like to
understand if the flows into the ingress qdisc can borrow from the root
and/or each other. Also, since the ingress qdisc is classless, how does
it work that each of the incoming flows are separately metered? (As I
understand it, filters only serve to guide packets into classes)
I know that the IMQ device offers a more sophisticated way to do this
but, for now, that device is not available to me.
I need answers to these specific questions, but I very much appreciate
any other information anyone would like to volunteer.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-08-05 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 20:59 Patrick Turley [this message]
2003-08-05 21:15 ` [LARTC] Parameters for the ingress qdisc? Stef Coene
2003-08-05 22:11 ` Patrick Turley
2003-08-06 18:18 ` Stef Coene
2003-08-06 18:41 ` Patrick Turley
2003-08-06 19:23 ` Stef Coene
2003-08-06 20:35 ` Stef Coene
2003-08-07 1:18 ` Martin A. Brown
2003-08-07 1:37 ` Martin A. Brown
2003-08-07 1:41 ` Patrick Turley
2003-08-07 1:51 ` Patrick Turley
2003-08-10 0:16 ` Martin A. Brown
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=marc-lartc-106011742407167@msgid-missing \
--to=pturley@rocksteady.com \
--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.