All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why isn't 1:1 getting the traffic? [filter question]
Date: Fri, 24 Feb 2006 23:01:07 +0000	[thread overview]
Message-ID: <20060224230107.GB18909@EIS> (raw)
In-Reply-To: <20060224175729.GF3794@mandriva.com>

On Fri, Feb 24, 2006 at 06:19:53PM -0300, Andreas wrote:
> >This was fairly obvious looking at your tc statistics output, where it
> >lists both 1:1 and 1:2 as roots with no parent. There can only be one
> >valid root class.
> 
> Why? I need two virtual circuits. I don't want the 90mbit class 
> interfere with the 200kbit class: no lending, no borrowing.

I think there can be more than just one root class - the question is 
just wether it makes sense or not. I prefer using one root class - 
after all, you only got one interface, and you have to make sure 
that you do not exceed the total interface capacity. Therefore, the 
root class is the interface limiter.

You can add isolated circuits to that root class easily; as long as 
all child classes of the root class have the same rate and ceil, 
no lending or borrowing between them will be done, simply because 
it is not necessary.

This way you get your desired features plus an overview on how much 
rate the physical interface actually has to offer - from my point 
of view, that's a win-win situation.

> It actually works if I use a *leaf* class as the target of the filter 
> (see my subsequent email). But this contradicts the documentation, which 
> even mentions one could gain speed by adding further filters to other 
> classes besides a root one.

I never got filters to work that do not point to leaf classes. Wether it 
is possible at all or not, I do not know. Maybe it was planned and turned 
out to be too complicated - maybe it is implemented but not working due 
to some undiscovered bug. I'm too lazy to look at the code right now.

I usually end up using iptables for classification; I find it to be 
far more userfriendly than the tc filters, and you can group filters 
any way you want.

Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-02-24 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 17:57 [LARTC] why isn't 1:1 getting the traffic? [filter question] Andreas Hasenack
2006-02-24 21:19 ` Andreas
2006-02-24 23:01 ` Andreas Klauer [this message]
2006-02-25  3:36 ` gypsy
2006-02-25 11:45 ` 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=20060224230107.GB18909@EIS \
    --to=andreas.klauer@metamorpher.de \
    --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.