netdev - Re: Single core gets pegged on multi-core PPTP server

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJuWrdu13Usax+bD3gtOkK=dhFyHQfMk5E7CLM=q8j_u92Hfkg@mail.gmail.com>
Date:	Fri, 20 Jan 2012 09:20:02 -0600
From:	Bradley Peterson <despite@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	paulus@...ba.org, linux-ppp@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Single core gets pegged on multi-core PPTP server

On Fri, Jan 20, 2012 at 12:16 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> Le jeudi 19 janvier 2012 à 16:35 -0600, Bradley Peterson a écrit :
>> Hello,
>>
>> I am trying to test the capacity of a linux PPTP server, both in
>> number of connections, and in packets per second.  I am using kernel
>> 2.6.38.8, with the ppp, pptp, and gre modules, and accel-pptp 0.8.3.
>> I have RPS, RFS, and XPS enabled on the network devices for SMP
>> support.
>>
>> But I'm seeing one CPU get pegged out with soft interrupt, while the
>> others are almost completely idle.
>>
>> In my current test, I'm starting 250 pptp connections from another
>> server, then running iperf across each connection.  The client machine
>> pegs out, sure, but I'm surprised the server pegs out a single CPU.
>> With RPS, I would expect softirq's to be more balanced.
>>
>> Where could the bottleneck be?  Do all ppp packets need to be
>> processed serially?
>>
>
> Hmmm, you need a more recent kernel or backport commit
> c6865cb3cc6f3c2857fa4c6f5fda2945d70b1e84
>    rps: Inspect GRE encapsulated packets to get flow hash
>
>    Crack open GRE packets in __skb_get_rxhash to compute 4-tuple hash on
>    in encapsulated packet.  Note that this is used only when the
>    __skb_get_rxhash is taken, in particular only when the device does
>    not compute provide the rxhash (ie. feature is disabled).
>
>    This was tested by creating a single GRE tunnel between two 16 core
>    AMD machines.  200 netperf TCP_RR streams were ran with 1 byte
>    request and response size.
>
>    Without patch: 157497 tps, 50/90/99% latencies 1250/1292/1364 usecs
>    With patch: 325896 tps, 50/90/99% latencies 603/848/1169
>
>    Signed-off-by: Tom Herbert <therbert@...gle.com>
>    Signed-off-by: David S. Miller <davem@...emloft.net>
>
>
>
> And make sure you disabled hardware rxhash (if your NIC provides it)
>
>

Thank you, I had missed the work on RPS with encapsulated packets.  I
will try a newer kernel.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html