From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: <eric.dumazet@gmail.com>, <netdev@vger.kernel.org>,
<sowmini.varadhan@oracle.com>, <ilant@mellanox.com>
Subject: Re: [PATCH RFC ipsec-next 2/2] xfrm: Add a dummy network device for napi.
Date: Mon, 30 Jan 2017 12:45:30 +0100 [thread overview]
Message-ID: <20170130114530.GT30338@gauss.secunet.com> (raw)
In-Reply-To: <20170127.095349.597744818419458840.davem@davemloft.net>
On Fri, Jan 27, 2017 at 09:53:49AM -0500, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Fri, 27 Jan 2017 06:46:38 -0800
>
> > On Fri, 2017-01-27 at 08:19 +0100, Steffen Klassert wrote:
> >> This patch adds a dummy network device so that we can
> >> use gro_cells for IPsec GRO. With this, we handle IPsec
> >> GRO with no impact on the generic networking code.
> >>
> >> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
> >> ---
> >> net/xfrm/xfrm_input.c | 12 +++++++++++-
> >> 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > That is nice ;)
>
> I like it too.
I've applied both to ipsec-next, thanks for all the feedback!
prev parent reply other threads:[~2017-01-30 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 7:19 [PATCH RFC ipsec-next v2] IPsec GRO Steffen Klassert
2017-01-27 7:19 ` [PATCH RFC ipsec-next 1/2] net: Drop secpath on free after gro merge Steffen Klassert
2017-01-27 7:19 ` [PATCH RFC ipsec-next 2/2] xfrm: Add a dummy network device for napi Steffen Klassert
2017-01-27 14:46 ` Eric Dumazet
2017-01-27 14:53 ` David Miller
2017-01-27 15:25 ` Eric Dumazet
2017-01-27 15:26 ` David Miller
2017-01-30 11:45 ` 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=20170130114530.GT30338@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).