aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/filter.txt
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2014-10-10 15:09:51 -0400
committerDavid S. Miller <davem@davemloft.net>2014-10-10 15:09:51 -0400
commit3ab52c69282fbc7384fe7e9d14f68ce11040feac (patch)
treeca97b979d908b286cc28449dfa887bbb9071ee58 /Documentation/networking/filter.txt
parentMerge branch 'xgene' (diff)
parentmacvlan: optimize the receive path (diff)
downloadlinux-dev-3ab52c69282fbc7384fe7e9d14f68ce11040feac.tar.xz
linux-dev-3ab52c69282fbc7384fe7e9d14f68ce11040feac.zip
Merge branch 'macvlan'
Jason Baron says: ==================== macvlan: optimize receive path So after porting this optimization to net-next, I found that the netperf results of TCP_RR regress right at the maximum peak of transactions/sec. That is as I increase the number of threads via the first argument to super_netperf, the number of transactions/sec keep increasing, peak, and then start decreasing. It is right at the peak, that I see a small regression with this patch (see results in patch 2/2). Without the patch, the ksoftirqd threads are the top cpu consumers threads on the system, since the extra 'netif_rx()', is queuing more softirq work, whereas with the patch, the ksoftirqd threads are below all of the 'netserver' threads in terms of their cpu usage. So there appears to be some interaction between how softirqs are serviced at the peak here and this patch. I think the test results are still supportive of this approach, but I wanted to be clear on my findings. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions