netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Tom Herbert <tom@herbertland.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/4] tcp: better smp listener behavior
Date: Tue, 13 Oct 2015 11:28:13 +0200	[thread overview]
Message-ID: <561CCEAD.206@iogearbox.net> (raw)
In-Reply-To: <20151013092223.GE11304@distanz.ch>

On 10/13/2015 11:22 AM, Tobias Klauser wrote:
> On 2015-10-09 at 20:02:47 +0200, Daniel Borkmann <daniel@iogearbox.net> wrote:
>> On 10/09/2015 12:50 PM, Eric Dumazet wrote:
>>> On Thu, 2015-10-08 at 20:42 -0700, Tom Herbert wrote:
>>>> On Thu, Oct 8, 2015 at 8:37 AM, Eric Dumazet <edumazet@google.com> wrote:
>>>>> As promised in last patch series, we implement a better SO_REUSEPORT
>>>>> strategy, based on cpu affinities if selected by the application.
>>>>>
>>>>> We also moved sk_refcnt out of the cache line containing the lookup
>>>>> keys, as it was considerably slowing down smp operations because
>>>>> of false sharing. This was simpler than converting listen sockets
>>>>> to conventional RCU (to avoid sk_refcnt dirtying)
>>>>>
>>>>> Could process 6.0 Mpps SYN instead of 4.2 Mpps on my test server.
>>>>>
>>>> Is this IPv4, IPv6, or some combination of the two ? :-)
>>>
>>> IPv4 only (mostly because I was using trafgen and its csumtcp() only
>>> deals with IPv4 and I am lazy)
>>
>> Agreed, will fix that in trafgen. ;) Thanks!
>
> Daniel, I'd have som preliminary patches for trafgen ready to introduce
> the csumudp6 and csumtcp6 trafgen helper functions (UDP/TCP checksum
> using IPv6 pseudo headers). If you want I can push them after some
> further testing later today.

Was off yesterday, so looks like you beat me to it. So, yes, perfect,
please do! :)

> Eric, would these to helpers be sufficient for your use case or do you
> need any additional trafgen functionality?

  reply	other threads:[~2015-10-13  9:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 15:37 [PATCH net-next 0/4] tcp: better smp listener behavior Eric Dumazet
2015-10-08 15:37 ` [PATCH net-next 1/4] net: SO_INCOMING_CPU setsockopt() support Eric Dumazet
2015-10-08 16:03   ` Tom Herbert
2015-10-08 16:29     ` Eric Dumazet
2015-10-08 16:44       ` Tom Herbert
2015-10-08 17:00         ` Eric Dumazet
2015-10-08 17:10           ` Tom Herbert
2015-10-08 16:50       ` Eric Dumazet
2015-10-08 16:07   ` kbuild test robot
2015-10-08 20:53   ` Tom Herbert
2015-10-08 21:17     ` Eric Dumazet
2015-10-08 15:37 ` [PATCH net-next 2/4] net: align sk_refcnt on 128 bytes boundary Eric Dumazet
2015-10-08 16:19   ` kbuild test robot
2015-10-08 15:37 ` [PATCH net-next 3/4] net: shrink struct sock and request_sock by 8 bytes Eric Dumazet
2015-10-08 16:31   ` kbuild test robot
2015-10-08 15:37 ` [PATCH net-next 4/4] tcp: shrink tcp_timewait_sock " Eric Dumazet
2015-10-09  3:42 ` [PATCH net-next 0/4] tcp: better smp listener behavior Tom Herbert
2015-10-09 10:50   ` Eric Dumazet
2015-10-09 14:29     ` Eric Dumazet
2015-10-09 14:49       ` Eric Dumazet
2015-10-09 18:02     ` Daniel Borkmann
2015-10-09 18:12       ` Eric Dumazet
2015-10-13  9:22       ` Tobias Klauser
2015-10-13  9:28         ` Daniel Borkmann [this message]
2015-10-13 10:01           ` Tobias Klauser
2015-10-13 14:17             ` 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=561CCEAD.206@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=tklauser@distanz.ch \
    --cc=tom@herbertland.com \
    /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).