netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Sowmini Varadhan <sowmini.varadhan@oracle.com>,
	Ilan Tayari <ilant@mellanox.com>
Subject: Re: [PATCH RFC ipsec-next] IPsec offload, part one
Date: Wed, 18 Jan 2017 08:59:44 +0100	[thread overview]
Message-ID: <20170118075944.GD3541@gauss.secunet.com> (raw)
In-Reply-To: <1483518230-6777-1-git-send-email-steffen.klassert@secunet.com>

On Wed, Jan 04, 2017 at 09:23:45AM +0100, Steffen Klassert wrote:
> This is the first part of the IPsec offload work we
> talked at the IPsec workshop at the last netdev
> conference. I plan to apply this to ipsec-next
> after this round of review.
> 
> Patch 1 and 2 try to avoid skb linearization in
> the ESP layer.
> 
> Patch 3 introduces a hepler to seup the esp trailer.

I have not received any comments about patches 1-3,
so I've applied them to ipsec-next.

> 
> Patch 4 prepares the generic network code for
> IPsec GRO. The main reason why we need this, is
> that we need to reinject the decrypted inner
> packet back to the GRO layer.
> 
> Patch 5 introduces GRO handlers for ESP, GRO
> can enabled with a IPsec offload config option.
> This config option will also be used for the
> upcomming hardware offload.

Patches 4 and 5 will be refactored according to
the comments from Eric.

      parent reply	other threads:[~2017-01-18  7:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  8:23 [PATCH RFC ipsec-next] IPsec offload, part one Steffen Klassert
2017-01-04  8:23 ` [PATCH RFC ipsec-next 1/5] esp4: Avoid skb_cow_data whenever possible Steffen Klassert
2017-01-04  8:23 ` [PATCH RFC ipsec-next 2/5] esp6: " Steffen Klassert
2017-01-04  8:23 ` [PATCH RFC ipsec-next 3/5] esp: Introduce a helper to setup the trailer Steffen Klassert
2017-01-04  8:23 ` [PATCH RFC ipsec-next 4/5] net: Prepare for IPsec GRO Steffen Klassert
2017-01-04 12:34   ` Eric Dumazet
2017-01-04 13:26     ` Steffen Klassert
2017-01-09  9:59       ` Steffen Klassert
2017-01-04  8:23 ` [PATCH RFC ipsec-next 5/5] esp: Add a software GRO codepath Steffen Klassert
2017-01-18  7:59 ` Steffen Klassert [this message]

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=20170118075944.GD3541@gauss.secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=ilant@mellanox.com \
    --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 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).