DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Igor Russkikh <Igor.Russkikh@aquantia.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	Pavel Belous <Pavel.Belous@aquantia.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/6] add MACSEC hw offload to atlantic PMD
Date: Thu, 18 Apr 2019 15:28:38 +0100	[thread overview]
Message-ID: <06d7e1e6-5078-cbd5-4afd-1850ad1a03bf@intel.com> (raw)
In-Reply-To: <cover.1555587238.git.igor.russkikh@aquantia.com>

On 4/18/2019 12:39 PM, Igor Russkikh wrote:
> This patchset implements MACSEC hardware offload configuration in
> Atlantic PMD via experimental PMD API.
> 
> There is an agreement to work on 19.08 timeframe for the generic
> MACSEC API inside of rte_security.
> 
> v3 changes after Ferruh's comments:
> - Fixed per-patch build by rearranging patch 2/4.
> - Added documentation comments into the API header.
> 
> v2 changes:
> - Removed public API changes for macsec, leave only PMD experimental
>   API for MACSEC in a form, similar to what ixgbe driver provides.
> - Joined doc and features update into commit where macsec features
>   gets actually enabled
> 
> Igor Russkikh (1):
>   net/atlantic: bump internal driver version
> 
> Pavel Belous (5):
>   net/atlantic: macsec hardware structures declaration
>   net/atlantic: enable macsec configuration
>   net/atlantic: macsec firmware interface
>   net/atlantic: interrupt handling and macsec configuration
>   net/atlantic: implement macsec statistics

Series applied to dpdk-next-net/master, thanks.

(release notes patch squashed into this one)

  parent reply	other threads:[~2019-04-18 14:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 11:39 Igor Russkikh
2019-04-18 11:39 ` Igor Russkikh
2019-04-18 11:39 ` [dpdk-dev] [PATCH v3 1/6] net/atlantic: macsec hardware structures declaration Igor Russkikh
2019-04-18 11:39   ` Igor Russkikh
2019-04-18 11:39 ` [dpdk-dev] [PATCH v3 2/6] net/atlantic: enable macsec configuration Igor Russkikh
2019-04-18 11:39   ` Igor Russkikh
2019-04-18 11:39 ` [dpdk-dev] [PATCH v3 3/6] net/atlantic: macsec firmware interface Igor Russkikh
2019-04-18 11:39   ` Igor Russkikh
2019-04-18 11:39 ` [dpdk-dev] [PATCH v3 4/6] net/atlantic: interrupt handling and macsec configuration Igor Russkikh
2019-04-18 11:39   ` Igor Russkikh
2019-04-18 11:40 ` [dpdk-dev] [PATCH v3 5/6] net/atlantic: implement macsec statistics Igor Russkikh
2019-04-18 11:40   ` Igor Russkikh
2019-04-18 11:40 ` [dpdk-dev] [PATCH v3 6/6] net/atlantic: bump internal driver version Igor Russkikh
2019-04-18 11:40   ` Igor Russkikh
2019-04-18 11:56 ` [dpdk-dev] [PATCH v3 0/6] add MACSEC hw offload to atlantic PMD Ferruh Yigit
2019-04-18 11:56   ` Ferruh Yigit
2019-04-18 12:27   ` Igor Russkikh
2019-04-18 12:27     ` Igor Russkikh
2019-04-18 14:28 ` Ferruh Yigit [this message]
2019-04-18 14:28   ` Ferruh Yigit

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=06d7e1e6-5078-cbd5-4afd-1850ad1a03bf@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Igor.Russkikh@aquantia.com \
    --cc=Pavel.Belous@aquantia.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=thomas@monjalon.net \
    /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).