From: Dmitry Popov <dp@highloadlab.com>
To: "David S. Miller" <davem@davemloft.net>,
William.Allen.Simpson@gmail.com,
Eric Dumazet <eric.dumazet@gmail.com>,
Andreas Petlund <apetlund@simula.no>,
Shan Wei <shanwei@cn.fujitsu.co
Subject: [PATCH 0/5] tcp: ipv4 listen state scaling
Date: Wed, 27 Oct 2010 17:23:24 +0400 [thread overview]
Message-ID: <AANLkTikmNCogLY3ZVhtfxOnSpWdPMq1YBCM3ZprkxEsP@mail.gmail.com> (raw)
*Note: this patch depends on "[PATCH] tcp: md5 signature check scaling"*
Hi.
The problem with current TCP stack implementation is that it locks
socket in tcp_v4_rcv on each incoming packet. However, incoming SYNs
may be processed in parallel with syncookies. And it helps a lot under
synflood. This proposed patch serie fixes this problem, but (as for
now) for ipv4 only.
6-core Xeon with 6 RX queues on NIC:
without patch: 530k syn-pkts/s;
with patch: 1620k syn-pkts/s.
Discussion?
reply other threads:[~2010-10-27 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTikmNCogLY3ZVhtfxOnSpWdPMq1YBCM3ZprkxEsP@mail.gmail.com \
--to=dp@highloadlab.com \
--cc=William.Allen.Simpson@gmail.com \
--cc=apetlund@simula.no \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=shanwei@cn.fujitsu.co \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).