netdev - Re: ipsec impact on performance

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 1 Dec 2015 10:50:31 -0800
From:	Rick Jones <rick.jones2@....com>
To:	Sowmini Varadhan <sowmini.varadhan@...cle.com>
Cc:	netdev@...r.kernel.org, linux-crypto@...r.kernel.org
Subject: Re: ipsec impact on performance

On 12/01/2015 10:45 AM, Sowmini Varadhan wrote:
> On (12/01/15 10:17), Rick Jones wrote:
>>
>> What do the perf profiles show?  Presumably, loss of TSO/GSO means
>> an increase in the per-packet costs, but if the ipsec path
>> significantly increases the per-byte costs...
>
> For ESP-null, there's actually very little work to do - we just
> need to add the 8 byte ESP header with an spi and a seq#.. no
> crypto work to do.. so the overhead *should* be minimal, else
> we've painted ourself into a corner where we can't touch anything
> including TCP options like md5.

Something of a longshot, but are you sure you are still getting 
effective CKO/GRO on the receiver?

rick jones
--
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