From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 00/10][pull request] 10GbE Intel Wired LAN Driver Updates 2018-01-23
Date: Wed, 24 Jan 2018 14:25:05 -0500 (EST) [thread overview]
Message-ID: <20180124.142505.18939180273833794.davem@davemloft.net> (raw)
In-Reply-To: <CAL3LdT7zgVtpFXYO4pPWDbKwYTmj98oirMr500MKAMmtMOJ97w@mail.gmail.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 24 Jan 2018 08:59:23 -0800
> On Tue, Jan 23, 2018 at 10:20 AM, Jeff Kirsher
> <jeffrey.t.kirsher@intel.com> wrote:
>> This series contains updates to ixgbe only.
>>
>> Shannon Nelson provides an implementation of the ipsec hardware offload
>> feature for the ixgbe driver for these devices: x540, x550, 82599.
>>
>> The ixgbe NICs support ipsec offload for 1024 Rx and 1024 Tx Security
>> Associations (SAs), using up to 128 inbound IP addresses, and using the
>> rfc4106(gcm(aes)) encryption. This code does not yet support checksum
>> offload, or TSO in conjunction with the ipsec offload - those will be
>> added in the future.
>>
>> This code shows improvements in both packet throughput and CPU utilization.
>> For example, here are some quicky numbers that show the magnitude of the
>> performance gain on a single run of "iperf -c <dest>" with the ipsec
>> offload on both ends of a point-to-point connection:
>>
>> 9.4 Gbps - normal case
>> 7.6 Gbps - ipsec with offload
>> 343 Mbps - ipsec no offload
>
> Dave, looks like you pulled this in as well, correct? I did not
> receive notification.
My bad, I thought I did say I pulled it. :-)
prev parent reply other threads:[~2018-01-24 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 18:20 [net-next 00/10][pull request] 10GbE Intel Wired LAN Driver Updates 2018-01-23 Jeff Kirsher
2018-01-23 18:20 ` [net-next 01/10] ixgbe: clean up ipsec defines Jeff Kirsher
2018-01-23 18:21 ` [net-next 02/10] ixgbe: add ipsec register access routines Jeff Kirsher
2018-01-23 18:21 ` [net-next 03/10] ixgbe: add ipsec engine start and stop routines Jeff Kirsher
2018-01-23 18:21 ` [net-next 04/10] ixgbe: add ipsec data structures Jeff Kirsher
2018-01-23 18:21 ` [net-next 05/10] ixgbe: add ipsec offload add and remove SA Jeff Kirsher
2018-01-23 18:21 ` [net-next 06/10] ixgbe: restore offloaded SAs after a reset Jeff Kirsher
2018-01-23 18:21 ` [net-next 07/10] ixgbe: process the Rx ipsec offload Jeff Kirsher
2018-01-23 18:21 ` [net-next 08/10] ixgbe: process the Tx " Jeff Kirsher
2018-01-23 18:21 ` [net-next 09/10] ixgbe: ipsec offload stats Jeff Kirsher
2018-01-23 18:21 ` [net-next 10/10] ixgbe: register ipsec offload with the xfrm subsystem Jeff Kirsher
2018-01-24 16:59 ` [net-next 00/10][pull request] 10GbE Intel Wired LAN Driver Updates 2018-01-23 Jeff Kirsher
2018-01-24 19:25 ` David Miller [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=20180124.142505.18939180273833794.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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).