On 29.04, Alexei Starovoitov wrote: > On Thu, Apr 30, 2015 at 02:48:39AM +0200, Patrick McHardy wrote: > > Netfilter is based on hook chains. The cost when only using a single hook > > is minimal (as Pablo showed in his numbers), but even if only using > > TC and a single netfilter classifier chain, there has to be some relative > > ordering and the hooks provide this in a generic way. > > Unfortunately the numbers that Pablo shown are not measuring > the right thing. > > > 840203pps 403Mb/sec > > this is 20 times less than what they should be. > Something else were measured together with netif_receive_skb. > > I've applied these patches and see the following > for eth0 + ingress + u32: > > 18.0 Mpps > 21.43% kpktgend_0 [kernel.vmlinux] [k] __netif_receive_skb_core > 9.88% kpktgend_0 [kernel.vmlinux] [k] kfree_skb > 9.79% kpktgend_0 [cls_u32] [k] u32_classify > 9.16% kpktgend_0 [kernel.vmlinux] [k] _raw_spin_lock > 8.16% kpktgend_0 [kernel.vmlinux] [k] nf_iterate > 5.28% kpktgend_0 [sch_ingress] [k] handle_ing > 4.51% kpktgend_0 [sch_ingress] [k] ingress_enqueue > 4.42% kpktgend_0 [kernel.vmlinux] [k] tc_classify_compat > 3.16% kpktgend_0 [kernel.vmlinux] [k] nf_hook_slow > 3.01% kpktgend_0 [kernel.vmlinux] [k] ip_rcv > 2.70% kpktgend_0 [kernel.vmlinux] [k] tc_classify > > without these patches: > > 22.4 Mpps > 25.89% kpktgend_0 [kernel.vmlinux] [k] __netif_receive_skb_core > 14.41% kpktgend_0 [kernel.vmlinux] [k] kfree_skb > 14.05% kpktgend_0 [kernel.vmlinux] [k] _raw_spin_lock > 11.75% kpktgend_0 [cls_u32] [k] u32_classify > 6.48% kpktgend_0 [sch_ingress] [k] ingress_enqueue > 6.06% kpktgend_0 [kernel.vmlinux] [k] tc_classify_compat > 4.16% kpktgend_0 [kernel.vmlinux] [k] tc_classify > 3.77% kpktgend_0 [kernel.vmlinux] [k] ip_rcv > > clearly nf_iterate/nf_hook_slow are slowing things down. > > I've spent more than a week trying to speedup ingress qdisc > and, so far, got from 22.4 Mpps to 27.2 Mpps, > so this 'generalization' is totally not acceptable to me. > > You're right that for 10 years no one cared about performance > of ingress qdisc, but that doesn't mean it's a wrong abstraction > and wrong architecture. Now I care about its performance and > I hope other people will do too. The wrong abstraction is using a qdisc for ingress. An abstraction is not about performance. Why do you thing ingress exists? For queueing? Or as providing a hooking point for a bunch of broken (at ingress) actions? You're (one of) the one who painfully realized how broken any kind of packet mangling at that point is. The infrastructure is simply crap and always has been. > So please leave ingress qdisc alone, this 'generalization' > is too costly. Sorry, we are of the opinion that TC classifiers suck, so we will not leave that path alone :) You're numbers are well appreciated, we will fix this and return with better numbers. > That doesn't mean that netfilter shouldn't have its own hook > on ingress. Without patch 6, the set looks good. I don't agree. It would be preferable to optimize the single hook case not only for ingress's sake, but for all the already existing hooks. Cheers, Patrick -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
