From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: RE: [PATCH] doc: update release note for iavf AVX2 feature
Date: Mon, 3 Jul 2023 03:16:57 +0000 [thread overview]
Message-ID: <LV2PR11MB599702C357F5BAF0142F37BEF729A@LV2PR11MB5997.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1687997166-35215-1-git-send-email-wenzhuo.lu@intel.com>
> -----Original Message-----
> From: Wenzhuo Lu <wenzhuo.lu@intel.com>
> Sent: Thursday, June 29, 2023 8:06 AM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Subject: [PATCH] doc: update release note for iavf AVX2 feature
>
> Add the missed release note for iavf AVX2 feature in 23.07.
>
> Fixes: 5712bf9d6e14 ("net/iavf: add Tx AVX2 offload path")
>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> ---
> doc/guides/rel_notes/release_23_07.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_23_07.rst
> b/doc/guides/rel_notes/release_23_07.rst
> index 4459144..92c8a1d 100644
> --- a/doc/guides/rel_notes/release_23_07.rst
> +++ b/doc/guides/rel_notes/release_23_07.rst
> @@ -200,6 +200,12 @@ New Features
>
> Enhanced the GRO library to support TCP packets over IPv6 network.
>
> +* **Updated Intel iavf driver.**
> +
> + * Added new RX and TX paths in the AVX2 code to use HW offload
> + features. When the HW offload features are configured to be used, the
> + offload paths are chosen automatically. In parallel the support for HW
> + offload features was removed from the legacy AVX2 paths.
>
> Removed Items
> -------------
> --
> 1.8.3.1
Acked-by: Beilei Xing <beilei.xing@intel.com>
next prev parent reply other threads:[~2023-07-03 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 0:06 Wenzhuo Lu
2023-07-03 3:16 ` Xing, Beilei [this message]
2023-07-27 18:23 ` 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=LV2PR11MB599702C357F5BAF0142F37BEF729A@LV2PR11MB5997.namprd11.prod.outlook.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@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).