From: Marek Kierdelewicz <marek@piasta.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] u32 hashing filter - deletion problem!
Date: Wed, 12 Oct 2005 22:17:01 +0000 [thread overview]
Message-ID: <20051013001701.5a00d79c@cat> (raw)
Hi there,
I'm having a bit of a headache because of the u32 filter with hashing... My router administration system updates filter configuration differentially. Therefore I need to delete filters sometimes. I know that by deleting root class I'd make all filters go away, but I can't use that option in this particular case.
When I delete even a single u32 hashed filter I end up with non-functional u32 hashed filters. No band is classified by hashed u32 filters any more. The only thing that saves the day is a root class delete and full filter reload.
Test platform 1
---------------
tested kernels: 2.6.13.4 and 2.6.11-rc4 (both with SMP)
Hardware: 2 x Intel(R) Xeon(TM) CPU 2.40GHz with HT enabled
Test platform 2
---------------
tested kernels: 2.6.13.2
Hardware: AMD Athlon 900MHz
I don't know if it's important, but I'm using CPU cycle counter as a packet scheduler clock source on both systems.
Any comments? Should I go to the kernel dev group with this?
Cheers,
Marek Kierdelewicz
KoBa ISP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-10-12 22:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051013001701.5a00d79c@cat \
--to=marek@piasta.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox