dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 16/01/2020
Date: Thu, 16 Jan 2020 12:48:34 +0000	[thread overview]
Message-ID: <SN6PR11MB25581F1C6986AA92B483A7629A360@SN6PR11MB2558.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cf05506d-a1ce-4bef-25f7-914a4fc7dd76@intel.com>

Hi everyone,

> 
> * next-net-crypto
>   * Pull request sent
>   * There is a performance concern on some ipsec-gw patches,
>     they can go in -rc2 if the issue is solved
>   * CPU crypto from last release may be breaking ABI, need to confirm

AFAIK, there is no ABI breakage.

>     and discussed dummy variable is missing, may be postponed to next release

Not sure I understand last sentence, could the author explain
what dummy variables we are talking about.

Konstantin



  reply	other threads:[~2020-01-16 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 11:13 [dpdk-dev] DPDK Release Status Meeting 16/01/2020 Ferruh Yigit
2020-01-16 12:48 ` Ananyev, Konstantin [this message]
2020-01-16 13:17   ` Akhil Goyal
2020-01-16 13:39     ` Ananyev, Konstantin
2020-01-16 16:42       ` Akhil Goyal
2020-01-16 17:47         ` Ferruh Yigit
2020-01-16 13:19 ` Akhil Goyal
2020-01-16 17:50   ` Ferruh Yigit
2020-01-17 16:00 ` Honnappa Nagarahalli
2020-01-17 11:39 Ananyev, Konstantin

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=SN6PR11MB25581F1C6986AA92B483A7629A360@SN6PR11MB2558.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).