From: Eric Dumazet <eric.dumazet@gmail.com>
To: Eric Leblond <eric@regit.org>, Patrick McHardy <kaber@trash.net>,
Florian Westphal <fwestphal@astaro.com>
Cc: sclark46@earthlink.net, Kuzin Andrey <kuzinandrey@yandex.ru>,
Anders Nilsson Plymoth <lanilsson@gmail.com>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: [RFC] nfnetlink_queue not scalable
Date: Fri, 01 Jul 2011 09:00:10 +0200 [thread overview]
Message-ID: <1309503610.2515.18.camel@edumazet-laptop> (raw)
In-Reply-To: <1309455919.2515.3.camel@edumazet-laptop>
So I took a look at using several queues to spread load on several cpus,
and quickly found out some hot spots in our NFQUEUE processing, even
using cpu match, and correct cpu affinities.
iptables -N DISPATCH 2>/dev/null
iptables -F DISPATCH
for i in `seq 0 15`
do
iptables -A DISPATCH -m cpu --cpu $i -j NFQUEUE --queue-num $i
nfqnl_test -q $i &
done
iptables -A FORWARD -j DISPATCH
<stress load, 500.000 pps >
# cat /proc/net/netfilter/nfnetlink_queue
0 4855 0 2 65535 0 37638 886112 1
1 4858 0 2 65535 0 24530 886096 1
2 4862 0 2 65535 0 40666 886103 1
3 4866 0 2 65535 0 6480 830716 1
4 4870 0 2 65535 0 35957 886099 1
5 4872 0 2 65535 0 20001 886100 1
6 4875 0 2 65535 0 41656 886099 1
7 4877 0 2 65535 0 27196 886099 1
8 4879 0 2 65535 0 39173 886112 1
9 4881 0 2 65535 0 19840 886103 1
10 4883 0 2 65535 0 29339 850670 1
11 4885 0 2 65535 0 17933 886102 1
12 4887 0 2 65535 0 37680 886099 1
13 4889 0 2 65535 0 7327 830721 1
14 4891 0 2 65535 0 35577 886100 1
15 4893 0 2 65535 0 23854 886100 1
Number one offender is the nfnl_lock mutex hold each time we give a
verdict.
Number two is the nl_table_lock rwlock
# Events: 28K cycles
#
# Overhead Command Shared Object Symbol
# ........ ............ ........................... ...................................
#
10.60% nfqnl_test [kernel.kallsyms] [k] mutex_spin_on_owner
|
--- mutex_spin_on_owner
|
|--99.68%-- __mutex_lock_slowpath
| mutex_lock
| nfnl_lock
| nfnetlink_rcv
| netlink_unicast
| netlink_sendmsg
| sock_sendmsg
| __sys_sendmsg
| sys_sendmsg
| compat_sys_sendmsg
| compat_sys_socketcall
| sysenter_dispatch
| 0xffffe430
| nfnl_sendiov
| __set_verdict
| cb
| __nfnl_handle_msg
| nfnl_handle_packet
| nfq_handle_packet
| main
| __libc_start_main
| _start
--0.32%-- [...]
4.12% nfqnl_test [kernel.kallsyms] [k] __mutex_lock_slowpath
|
--- __mutex_lock_slowpath
|
|--99.68%-- mutex_lock
| nfnl_lock
Time to add RCU ;)
next prev parent reply other threads:[~2011-07-01 7:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 9:17 netfilter queue throughput slowdown Anders Nilsson Plymoth
2011-06-29 9:47 ` Eric Dumazet
2011-06-29 9:55 ` Anders Nilsson Plymoth
2011-06-29 10:08 ` Eric Dumazet
2011-06-30 6:20 ` Kuzin Andrey
2011-06-30 6:47 ` Eric Dumazet
2011-06-30 7:36 ` Kuzin Andrey
2011-06-30 11:34 ` Eric Dumazet
2011-06-30 11:59 ` Patrick McHardy
2011-06-30 15:15 ` Eric Dumazet
2011-06-30 14:32 ` Stephen Clark
2011-06-30 14:51 ` Patrick McHardy
2011-06-30 17:07 ` Eric Leblond
2011-06-30 17:45 ` Eric Dumazet
2011-06-30 18:08 ` Eric Leblond
2011-07-01 6:39 ` Amos Jeffries
2011-07-01 7:00 ` Eric Dumazet [this message]
2011-07-01 7:49 ` [RFC] nfnetlink_queue not scalable Florian Westphal
2011-07-01 15:27 ` [PATCH 1/2] nfnetlink: add RCU in nfnetlink_rcv_msg() Eric Dumazet
2011-07-01 14:11 ` Florian Westphal
2011-07-05 13:22 ` Patrick McHardy
2011-07-18 14:06 ` Patrick McHardy
2011-07-01 15:08 ` netfilter queue throughput slowdown Anders Nilsson Plymoth
2011-06-30 22:24 ` Sam Roberts
2011-07-01 4:53 ` Eric Dumazet
2011-06-30 22:26 ` Sam Roberts
2011-07-01 4:52 ` Eric Dumazet
2011-07-02 12:25 ` Pablo Neira Ayuso
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=1309503610.2515.18.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=eric@regit.org \
--cc=fwestphal@astaro.com \
--cc=kaber@trash.net \
--cc=kuzinandrey@yandex.ru \
--cc=lanilsson@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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.