| To: | jamal <hadi@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] Use nfmark as a key for u32 classifier |
| From: | "Catalin(ux aka Dino) BOIE" <util@xxxxxxxxxxxxxxx> |
| Date: | Mon, 8 Nov 2004 12:06:50 +0200 (EET) |
| Cc: | linux-net@xxxxxxxxxxxxxxx, lartc@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <1099669841.1026.18.camel@jzny.localdomain> |
| References: | <Pine.LNX.4.61.0411051317330.23651@webhosting.rdsbv.ro> <1099669841.1026.18.camel@jzny.localdomain> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
I think this is an ok midterm solution and should be applied. Thanks. One comment Catalin: Can you resend the patch make this a selectable choice via kconfig? Yes, of course.
Also, as a bonus, I will add a mask. Something like this:
tc filter add dev eth0 protocol ip parent 1:0 prio 5 u32 \
match mark 0x0090 0xffff \
^^^^^^
flowid 1:90It's ok? Eventually - we should kill this + the indev choices on u32 and move it up one so that we can have all filters capable of following filters from other classifiers. As a matter of fact we already have this feature but it is a little on the inefficient side at the moment.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Bug in ipv6_ifa_notify?, Herbert Xu |
|---|---|
| Next by Date: | Re: [Vpn-failover] [RFC] IPSEC failover - Netlink part, Ulrich Weber |
| Previous by Thread: | Re: [PATCH] Use nfmark as a key for u32 classifier, jamal |
| Next by Thread: | Re: [PATCH] Use nfmark as a key for u32 classifier, Patrick McHardy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |