From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: christoph.paasch@uclouvain.be, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Martin Topholm <mph@hoth.dk>, Florian Westphal <fw@strlen.de>,
Hans Schillstrom <hans.schillstrom@ericsson.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [RFC PATCH 0/2] Faster/parallel SYN handling to mitigate SYN floods
Date: Thu, 31 May 2012 15:24:13 +0200 [thread overview]
Message-ID: <1338470653.7747.178.camel@localhost> (raw)
In-Reply-To: <1338469811.2760.1345.camel@edumazet-glaptop>
On Thu, 2012-05-31 at 15:10 +0200, Eric Dumazet wrote:
> On Thu, 2012-05-31 at 14:58 +0200, Eric Dumazet wrote:
>
> >
> > How many different IP addresses are used by your generator ?
> >
> > Or maybe you disabled IP route cache ?
>
> With no route cache problems, I sustain 4 us per SYN packet, if all load
> serviced by one cpu only.
Yes that is also my experience, in this SYN-flood scenario one CPU does
a lot better. My old home brew AMD quad-core CPU also outperform, the
big testlab machine dual socket quad-core Nehalem.
The route cache problem, should not be too big with my SYN cookie
solution. I think... as tcp_v4_send_synack() handles alloc of a dst
route cache, but also releases it immediately afterwards.
How do you/I measure the usec per packet?
How do I disable the route cache?
What test tools do you use?
(I have modified pktgen to send TCP SYN packets)
(ps. I'll post my updated patch series, in a bit, and then I'll try not
to disturb your work on the fully parallel solution).
> perf profile is : (I have CONFIG_DEBUG_PAGEALLOC=y)
>
> + 9,55% ksoftirqd/0 [kernel.kallsyms] [k] sha_transform
> + 3,56% ksoftirqd/0 [kernel.kallsyms] [k] ip_route_input_common
> + 3,40% ksoftirqd/0 [kernel.kallsyms] [k] __ip_route_output_key
> + 3,28% ksoftirqd/0 [kernel.kallsyms] [k] __inet_lookup_established
> + 3,13% ksoftirqd/0 [kernel.kallsyms] [k] tg3_poll_work
> + 2,68% ksoftirqd/0 [kernel.kallsyms] [k] tcp_make_synack
> + 2,67% ksoftirqd/0 [kernel.kallsyms] [k] __netif_receive_skb
> + 2,51% ksoftirqd/0 [kernel.kallsyms] [k] ipt_do_table
> + 2,17% ksoftirqd/0 [kernel.kallsyms] [k] memcpy
> + 1,99% ksoftirqd/0 [kernel.kallsyms] [k] kernel_map_pages
> + 1,96% ksoftirqd/0 [kernel.kallsyms] [k] inet_csk_search_req
> + 1,69% ksoftirqd/0 [kernel.kallsyms] [k] tg3_recycle_rx.isra.36
> + 1,63% ksoftirqd/0 [kernel.kallsyms] [k] kmem_cache_free
> + 1,61% ksoftirqd/0 [kernel.kallsyms] [k] copy_user_generic_string
> + 1,49% ksoftirqd/0 [kernel.kallsyms] [k] kmem_cache_alloc
> + 1,47% ksoftirqd/0 [kernel.kallsyms] [k] ip_rcv
> + 1,11% ksoftirqd/0 [kernel.kallsyms] [k] tcp_v4_conn_request
> + 1,07% ksoftirqd/0 [kernel.kallsyms] [k] nf_iterate
> + 1,07% swapper [kernel.kallsyms] [k] sha_transform
> + 1,05% ksoftirqd/0 [kernel.kallsyms] [k] kfree
> + 1,05% ksoftirqd/0 [kernel.kallsyms] [k] skb_release_data
> + 0,99% ksoftirqd/0 [kernel.kallsyms] [k] __alloc_skb
> + 0,98% ksoftirqd/0 [kernel.kallsyms] [k] __kmalloc_node_track_caller
> + 0,97% ksoftirqd/0 [kernel.kallsyms] [k] netdev_alloc_frag
> + 0,96% ksoftirqd/0 [kernel.kallsyms] [k] dev_gro_receive
> + 0,94% ksoftirqd/0 [kernel.kallsyms] [k] inet_gro_receive
> + 0,85% ksoftirqd/0 [kernel.kallsyms] [k] build_skb
> + 0,85% ksoftirqd/0 [kernel.kallsyms] [k] cookie_v4_init_sequence
> + 0,85% ksoftirqd/0 [kernel.kallsyms] [k] ip_build_and_send_pkt
> + 0,84% ksoftirqd/0 [kernel.kallsyms] [k] __copy_skb_header
> + 0,82% ksoftirqd/0 [kernel.kallsyms] [k] nf_hook_slow
> + 0,77% ksoftirqd/0 [kernel.kallsyms] [k] __skb_clone
> + 0,73% ksoftirqd/0 [kernel.kallsyms] [k] tcp_v4_rcv
> + 0,72% ksoftirqd/0 [kernel.kallsyms] [k] xfrm_lookup
> + 0,69% ksoftirqd/0 [kernel.kallsyms] [k] dev_hard_start_xmit
> + 0,68% ksoftirqd/0 [kernel.kallsyms] [k] local_bh_enable
> + 0,67% ksoftirqd/0 [kernel.kallsyms] [k] tcp_gro_receive
> + 0,67% ksoftirqd/0 [kernel.kallsyms] [k] kfree_skb
> + 0,67% ksoftirqd/0 [kernel.kallsyms] [k] __probe_kernel_read
> + 0,67% ksoftirqd/0 [kernel.kallsyms] [k] skb_release_head_state
> + 0,66% ksoftirqd/0 [kernel.kallsyms] [k] __phys_addr
> + 0,66% ksoftirqd/0 [kernel.kallsyms] [k] ip_finish_output
> + 0,65% ksoftirqd/0 [kernel.kallsyms] [k] dst_release
> + 0,64% ksoftirqd/0 [kernel.kallsyms] [k] __ip_local_out
> + 0,61% ksoftirqd/0 [kernel.kallsyms] [k] packet_rcv_spkt
> + 0,57% ksoftirqd/0 [kernel.kallsyms] [k] __kfree_skb
next prev parent reply other threads:[~2012-05-31 13:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 11:52 [RFC PATCH 0/2] Faster/parallel SYN handling to mitigate SYN floods Jesper Dangaard Brouer
2012-05-28 11:52 ` [RFC PATCH 1/2] tcp: extract syncookie part of tcp_v4_conn_request() Jesper Dangaard Brouer
2012-05-28 11:52 ` [RFC PATCH 2/2] tcp: Early SYN limit and SYN cookie handling to mitigate SYN floods Jesper Dangaard Brouer
2012-05-29 19:37 ` Andi Kleen
2012-05-29 20:18 ` David Miller
2012-05-30 6:41 ` Eric Dumazet
2012-05-30 7:45 ` Jesper Dangaard Brouer
2012-05-30 8:15 ` Eric Dumazet
2012-05-30 9:24 ` Jesper Dangaard Brouer
2012-05-30 9:46 ` Eric Dumazet
2012-05-30 8:03 ` Hans Schillstrom
2012-05-30 8:24 ` Eric Dumazet
2012-05-30 11:14 ` Hans Schillstrom
2012-05-30 21:20 ` Rick Jones
2012-05-31 8:28 ` Eric Dumazet
2012-05-31 8:45 ` Hans Schillstrom
2012-05-31 14:09 ` Eric Dumazet
2012-05-31 15:31 ` Hans Schillstrom
2012-05-31 17:16 ` Eric Dumazet
2012-05-28 16:14 ` [RFC PATCH 0/2] Faster/parallel SYN " Christoph Paasch
2012-05-29 20:17 ` Jesper Dangaard Brouer
2012-05-29 20:36 ` Christoph Paasch
2012-05-30 8:44 ` Jesper Dangaard Brouer
2012-05-30 8:50 ` Eric Dumazet
2012-05-30 8:53 ` Christoph Paasch
2012-05-30 22:40 ` Jesper Dangaard Brouer
2012-05-31 12:51 ` Jesper Dangaard Brouer
2012-05-31 12:58 ` Eric Dumazet
2012-05-31 13:04 ` Jesper Dangaard Brouer
2012-05-31 13:10 ` Eric Dumazet
2012-05-31 13:24 ` Jesper Dangaard Brouer [this message]
2012-05-30 4:45 ` Eric Dumazet
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=1338470653.7747.178.camel@localhost \
--to=jbrouer@redhat.com \
--cc=andi@firstfloor.org \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=hans.schillstrom@ericsson.com \
--cc=mph@hoth.dk \
--cc=netdev@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 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.