All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] prio/pref weirdness
Date: Mon, 08 Apr 2002 15:55:35 +0000	[thread overview]
Message-ID: <marc-lartc-101828164332050@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101827773328056@msgid-missing>

It is bug I described a year ago. It is due to a bit ... weird
system used in tc filters and u32. There is global table of
all u32 hashed and it is looked up for each filter id - thus 
it will display them over and over ....
You can mitigate it by using "show pref N" so see only part
you are interested in.
devik

On Mon, 8 Apr 2002, Mihai RUSU wrote:

> Hi
> 
> I am playing with filters and cbq/htb and I have found this strange thing.
> Add some filters using the prio/pref (they seem an alias to me)
> parameter like:
> tc filter add dev eth0 protocol ip parent 1: pref 5 u32 match ip dst 1.2.3.4
> tc filter add dev eth0 protocol ip parent 1: pref 10 u32 match ip dst 2.3.4.5
> 
> And try tc filter show dev eth0, you will see that every filter you have
> is multiplied by the number of different prio/pref values you have used.
> 
> Thus it looks like you would do this:
> 
> tc filter add dev eth0 protocol ip parent 1: pref 5 u32 match ip dst 1.2.3.4
> tc filter add dev eth0 protocol ip parent 1: pref 5 u32 match ip dst 2.3.4.5
> 
> tc filter add dev eth0 protocol ip parent 1: pref 10 u32 match ip dst 1.2.3.4
> tc filter add dev eth0 protocol ip parent 1: pref 10 u32 match ip dst 2.3.4.5
> 
> Why is that? Is it a tc bug? Or is it normal? What it happens if I use
> filters of different pref/prio ? In which order are they checked ?
> 
> 
> Thanks
> 
> ----------------------------
> Mihai RUSU
> 
> Disclaimer: Any views or opinions presented within this e-mail are solely
> those of the author and do not necessarily represent those of any company,
> unless otherwise specifically stated.
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 
> 

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

  reply	other threads:[~2002-04-08 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 14:55 [LARTC] prio/pref weirdness Mihai RUSU
2002-04-08 15:55 ` Martin Devera [this message]
2002-04-09  8:54 ` Mihai RUSU
2002-04-09  9:03 ` Martin Devera

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-101828164332050@msgid-missing \
    --to=devik@cdi.cz \
    --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.