From: "Zhang, Fan" <fanzhang.oss@gmail.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>, kai.ji@intel.com
Cc: dev@dpdk.org, Ciara Power <ciara.power@intel.com>
Subject: Re: [PATCH v3] doc: support IPsec Multi-buffer lib v1.3
Date: Thu, 10 Nov 2022 16:44:03 +0000 [thread overview]
Message-ID: <49d58397-cdc2-14ae-8b0e-c8df44e3c6ab@gmail.com> (raw)
In-Reply-To: <20221110110707.4162335-1-pablo.de.lara.guarch@intel.com>
Hi Pablo,
On 11/10/2022 11:07 AM, Pablo de Lara wrote:
> Updated AESNI MB and AESNI GCM, KASUMI, ZUC and SNOW3G PMD documentation
> guides with information about the latest Intel IPSec Multi-buffer
> library supported.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Acked-by: Ciara Power <ciara.power@intel.com>
>
> ---
> -v3: Fixed library version from 1.2 to 1.3 in one line
> -v2: Removed repeated word 'the'
> ---
>
This to me is a great change that formally recommending one PMD over the
other for performance reason.
Do you think release notes should be updated to shut out this change?
Regards,
Fan
Other than that
Acked-by: Fan Zhang <fanzhang.oss@gmail.com>
next prev parent reply other threads:[~2022-11-10 16:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 18:33 [PATCH] " Pablo de Lara
2022-11-09 18:39 ` [PATCH v2] " Pablo de Lara
2022-11-10 9:38 ` [EXT] " Akhil Goyal
2022-11-10 10:43 ` Power, Ciara
2022-11-10 11:07 ` [PATCH v3] " Pablo de Lara
2022-11-10 11:17 ` Dooley, Brian
2022-11-10 11:39 ` Ji, Kai
2022-11-11 16:24 ` De Lara Guarch, Pablo
2022-11-10 16:44 ` Zhang, Fan [this message]
2022-11-12 11:26 ` [PATCH v4] " Pablo de Lara
2022-11-14 23:34 ` Ji, Kai
2022-11-15 9:24 ` Akhil Goyal
2022-11-15 17:11 ` [dpdk-dev v5] " Kai Ji
2022-11-15 20:17 ` Zhang, Fan
2022-11-16 12:06 ` [dpdk-dev v6] " Kai Ji
2022-11-17 12:16 ` Kai Ji
2022-11-21 6:57 ` [EXT] " Akhil Goyal
2022-11-21 10:57 ` Zhang, Fan
2022-11-21 11:35 ` Akhil Goyal
2022-11-21 13:52 ` Zhang, Fan
2022-11-21 16:35 ` [dpdk-dev v7] " Kai Ji
2022-11-22 11:57 ` Thomas Monjalon
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=49d58397-cdc2-14ae-8b0e-c8df44e3c6ab@gmail.com \
--to=fanzhang.oss@gmail.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.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).