From: Rafal Maszkowski rzm@icm.edu.pl
To: lartc@vger.kernel.org
Subject: [LARTC] how many u32 filters?
Date: Wed, 01 Nov 2000 01:28:13 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216876@msgid-missing> (raw)
<PRE>I asked already on netdev. Maybe my description is too obscure? Could you try
to answer or help me to make the question clearer?
I am adding u32 filters with commands like:
tc filter add dev eth0 parent 10:0 protocol ip prio 100 handle 800::2 u32 match ip dst 10.30.40.3 flowid 10:2
...
getting:
filter parent 10: protocol ip pref 100 u32
filter parent 10: protocol ip pref 100 u32 fh 800: ht divisor 1
filter parent 10: protocol ip pref 100 u32 fh 800::2 order 2 key ht 800 bkt 0 flowid 10:2
match 0a1e2803/ffffffff at 16
filter parent 10: protocol ip pref 100 u32 fh 800::3 order 3 key ht 800 bkt 0 flowid 10:3
match 0a1e2809/ffffffff at 16
...
and then I can delete them with
tc filter del dev eth0 parent 10:0 protocol ip prio 100 handle 800::2 u32 match ip dst 10.30.40.3 flowid 10:2
It looks like the highest handle is 800::7ff (or maybe fff) and there may be
only 2048 (4k?) filters with unique handles. They have to be unique to make
single filters deletions possible.
Is it possible to setup the u32 filters in such a way that 64k or more unique
handles would be available?
I do not know if a single system would be able to carry such load but maybe it
is possible, I hope to be able to test it in the future. A company I work for
in principle may need tens of thousands of limits, putting every 2k of limits
on a separate machine would be limiting us to much.
R.
--
W iskier krzesaniu ¿ywem/Materia³ to rzecz g³ówna
</PRE>
next reply other threads:[~2000-11-01 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 1:28 Rafal [this message]
2000-11-05 21:55 ` [LARTC] how many u32 filters? bert
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-98373938216876@msgid-missing \
--to=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.