All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Turley <pturley@rocksteady.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Parameters for the ingress qdisc?
Date: Tue, 05 Aug 2003 22:11:28 +0000	[thread overview]
Message-ID: <marc-lartc-106012161711855@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106011742407167@msgid-missing>

Thank you very much for the link. That information was very helpful and
has given me a lot of insight.

Of course, the more I know, the more questions occur...

I try not to be a nuisance, so I've been doing a lot of research and I
thought I'd already found all the important web sites for Linux traffic
control. I looked again, and I still can't find anything about "filter
policers" anywhere. I didn't find any description of a command line that
even suggested such a thing was possible. Can you please point me to
some more info about this, if any exists?

The fact that the filters are metering traffic flows implies that they
have are stateful. When using filters with egress queue hierarchies, it
was my understanding that no state was needed since all they do is
direct packets into classes. It sounds like my current understanding is
quite wrong.

BTW, we are working with a stock RedHat 7.3 2.4.20-18.7 kernel, and we
are VERY reluctant to apply patches of any kind, so we're just going to
work with whatever is available in the bits we download. We're
considering moving up to 2.4.21 to get IMQ, but that doesn't appear to
be available for RedHat 7.3 yet - in fact, this may force us to RedHat
9.0 (not a bad thing, really).

On Tue, 2003-08-05 at 16:15, Stef Coene wrote:
> On Tuesday 05 August 2003 22:59, Patrick Turley wrote:
> > I can't find any documentation on the paramaters for the ingress qdisc.
> > Can someone help me?
> >
> > ...
> The ingress qdisc itself has no parameters.  The only thing you can do is 
> using the policers.  I have a link with a patch to extend this : 
> http://www.cyberus.ca/~hadi/patches/action/
> Maybe this can help.
> 
> I have some more info about ingress in my mail files, but I have to sort it 
> out and put it somewhere on docum.org.  But I still didn't found the the time 
> to do so.
> 
> Stef

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-08-05 22:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 20:59 [LARTC] Parameters for the ingress qdisc? Patrick Turley
2003-08-05 21:15 ` Stef Coene
2003-08-05 22:11 ` Patrick Turley [this message]
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-106012161711855@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.