Adding a tc filter creates a blank hash table too. why?

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am adding 5 rules in 5 different buckets within a same hashtable.
However, when I view the filter list I see 5 different hashtables also created.
I am unable to understand why that is so?

My config commands are :

tc qdisc add dev eth15 root handle 1: htb default 2

tc class add dev eth15 parent 1: classid 1:1 htb rate 10mbit

tc class add dev eth15 parent 1:1 classid 1:2 htb rate 1kbit
tc class add dev eth15 parent 1:1 classid 1:3 htb rate 2mbit


tc filter add dev eth15 parent 1:0 protocol ip handle 1: u32 divisor 256

tc filter add dev eth15 protocol ip parent 1:0 handle ::1 u32 ht 1:1
match ip src 10.21.1.1 flowid 1:3
tc filter add dev eth15 protocol ip parent 1:0 handle ::1 u32 ht 1:2
match ip src 10.21.1.2 flowid 1:3
tc filter add dev eth15 protocol ip parent 1:0 handle ::1 u32 ht 1:3
match ip src 10.21.1.3 flowid 1:3
tc filter add dev eth15 protocol ip parent 1:0 handle ::1 u32 ht 1:4
match ip src 10.21.1.4 flowid 1:3
tc filter add dev eth15 protocol ip parent 1:0 handle ::1 u32 ht 1:5
match ip src 10.21.1.5 flowid 1:3


Output of 'tc filter show dev eth15' is

filter parent 1: protocol ip pref 49147 u32
filter parent 1: protocol ip pref 49147 u32 fh 805: ht divisor 1
filter parent 1: protocol ip pref 49148 u32
filter parent 1: protocol ip pref 49148 u32 fh 804: ht divisor 1
filter parent 1: protocol ip pref 49149 u32
filter parent 1: protocol ip pref 49149 u32 fh 803: ht divisor 1
filter parent 1: protocol ip pref 49150 u32
filter parent 1: protocol ip pref 49150 u32 fh 802: ht divisor 1
filter parent 1: protocol ip pref 49151 u32
filter parent 1: protocol ip pref 49151 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 49152 u32
filter parent 1: protocol ip pref 49152 u32 fh 1: ht divisor 256
filter parent 1: protocol ip pref 49152 u32 fh 1:1:1 order 1 key ht 1
bkt 1 flowid 1:3
  match 0a150101/ffffffff at 12
filter parent 1: protocol ip pref 49152 u32 fh 1:2:1 order 1 key ht 1
bkt 2 flowid 1:3
  match 0a150102/ffffffff at 12
filter parent 1: protocol ip pref 49152 u32 fh 1:3:1 order 1 key ht 1
bkt 3 flowid 1:3
  match 0a150103/ffffffff at 12
filter parent 1: protocol ip pref 49152 u32 fh 1:4:1 order 1 key ht 1
bkt 4 flowid 1:3
  match 0a150104/ffffffff at 12
filter parent 1: protocol ip pref 49152 u32 fh 1:5:1 order 1 key ht 1
bkt 5 flowid 1:3
  match 0a150105/ffffffff at 12
filter parent 1: protocol ip pref 49152 u32 fh 800: ht divisor 1




my question regarding those 801,802,803,804,805 hashtable on the top.
Why they are there ? how to avoid them?


-Akshat
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux