From: Steffen Klassert <steffen.klassert@secunet.com>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: <netdev@vger.kernel.org>, <linux-crypto@vger.kernel.org>
Subject: Re: ipsec impact on performance
Date: Thu, 3 Dec 2015 09:45:08 +0100 [thread overview]
Message-ID: <20151203084508.GD14008@secunet.com> (raw)
In-Reply-To: <20151202120538.GJ23178@oracle.com>
On Wed, Dec 02, 2015 at 07:05:38AM -0500, Sowmini Varadhan wrote:
> On (12/02/15 07:53), Steffen Klassert wrote:
> >
> > I'm currently working on a GRO/GSO codepath for IPsec too. The GRO part
> > works already. I decapsulate/decrypt the packets on layer2 with a esp GRO
> > callback function and reinject them into napi_gro_receive(). So in case
> > the decapsulated packet is TCP, GRO can aggregate big packets.
>
> Would you be able to share your patch with me? I'd like to give that a try
> just to get preliminary numbers (and I could massage it as needed
> for transport mode too).
I've got the final bits to work today, I can do async crypto now.
I can push the patches to a public tree after some polishing.
But I have to warn, it has still bugs and no usefull commit messages.
I did a first test with forwaring esp in tunnel mode. The crypto
algorithm I used was:
pcrypt(echainiv(authenc(hmac(sha1-ssse3),cbc-aes-aesni)))
Result:
iperf -c 10.0.0.12 -t 60
------------------------------------------------------------
Client connecting to 10.0.0.12, TCP port 5001
TCP window size: 45.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.0.12 port 39380 connected with 10.0.0.12 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-60.0 sec 32.8 GBytes 4.70 Gbits/sec
I provide more informatios as soon as the code is available.
>
> > Another thing, I thought about setting up an IPsec BoF/workshop at
> > netdev1.1. My main topic is GRO/GSO for IPsec. I'll send out a mail
> > to the list later this week to see if there is enough interest and
> > maybe some additional topics.
>
> Sounds like an excellent idea. I'm certainly interested.
Great, than we are at least two :)
next prev parent reply other threads:[~2015-12-03 8:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 17:59 ipsec impact on performance Sowmini Varadhan
2015-12-01 18:17 ` Rick Jones
2015-12-01 18:45 ` Sowmini Varadhan
2015-12-01 18:50 ` Rick Jones
2015-12-01 19:01 ` Sowmini Varadhan
2015-12-02 0:56 ` David Ahern
2015-12-02 1:09 ` Sowmini Varadhan
2015-12-02 1:25 ` David Ahern
2015-12-01 18:18 ` Tom Herbert
2015-12-01 18:37 ` Sowmini Varadhan
2015-12-02 11:56 ` David Laight
2015-12-02 12:11 ` Sowmini Varadhan
2015-12-02 12:41 ` David Laight
2015-12-02 13:25 ` Sowmini Varadhan
2015-12-02 20:50 ` Sowmini Varadhan
2015-12-02 21:07 ` Tom Herbert
2015-12-02 21:12 ` Sowmini Varadhan
2015-12-02 21:44 ` Tom Herbert
2015-12-02 21:47 ` Sowmini Varadhan
2015-12-02 22:01 ` Tom Herbert
2015-12-02 22:08 ` Sowmini Varadhan
2015-12-02 22:25 ` Eric Dumazet
2015-12-03 1:31 ` Rick Jones
2015-12-02 6:53 ` Steffen Klassert
2015-12-02 12:05 ` Sowmini Varadhan
2015-12-03 8:45 ` Steffen Klassert [this message]
2015-12-03 11:38 ` Sowmini Varadhan
2015-12-03 11:47 ` Steffen Klassert
2015-12-07 8:40 ` Steffen Klassert
2015-12-07 11:27 ` Sowmini Varadhan
2015-12-08 11:32 ` Steffen Klassert
2015-12-08 11:51 ` Sowmini Varadhan
2015-12-03 19:33 ` David Miller
2015-12-03 20:08 ` Eric Dumazet
2015-12-03 20:32 ` Sowmini Varadhan
2015-12-04 5:18 ` Sandy Harris
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=20151203084508.GD14008@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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 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.