From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Vamsi Attunuru <vattunuru@marvell.com>,
dev@dpdk.org
Subject: Re: [PATCH v4 3/3] net/octeon_ep: use AVX2 instructions for Rx
Date: Mon, 11 Dec 2023 17:35:22 +0530 [thread overview]
Message-ID: <CALBAE1PLNKhNwxW8kfd6s6oK_551yYDPiTKS2Tr1GMALkWcaoQ@mail.gmail.com> (raw)
In-Reply-To: <20231207064941.1256-3-pbhagavatula@marvell.com>
On Thu, Dec 7, 2023 at 2:03 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Optimize Rx routine to use AVX2 instructions when underlying
> architecture supports it.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> doc/guides/rel_notes/release_24_03.rst | 5 +
> drivers/net/octeon_ep/cnxk_ep_rx_avx.c | 123 +++++++++++++++++++++++++
> drivers/net/octeon_ep/meson.build | 12 +++
> drivers/net/octeon_ep/otx_ep_ethdev.c | 10 ++
> drivers/net/octeon_ep/otx_ep_rxtx.h | 6 ++
> 5 files changed, 156 insertions(+)
> create mode 100644 drivers/net/octeon_ep/cnxk_ep_rx_avx.c
>
> diff --git a/doc/guides/rel_notes/release_24_03.rst b/doc/guides/rel_notes/release_24_03.rst
> index 6f8ad27808..2191dd78e7 100644
> --- a/doc/guides/rel_notes/release_24_03.rst
> +++ b/doc/guides/rel_notes/release_24_03.rst
> @@ -55,6 +55,11 @@ New Features
> Also, make sure to start the actual text at the margin.
> =======================================================
>
> +* **Updated Marvell Octeon ep driver.**
> +
> + * Added SSE/AVX2 Rx routines.
> + * Updated Tx queue thresholds.
Please add little more info in Tx queue one.
Also, Split doc changes to respective patches.
next prev parent reply other threads:[~2023-12-11 12:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 16:03 [PATCH v2 1/3] net/octeon_ep: optimize Rx and Tx routines pbhagavatula
2023-11-25 16:03 ` [PATCH v2 2/3] net/octeon_ep: use SSE instructions for Rx routine pbhagavatula
2023-12-06 12:17 ` Jerin Jacob
2023-11-25 16:03 ` [PATCH v2 3/3] net/octeon_ep: use AVX2 instructions for Rx pbhagavatula
2023-12-06 12:12 ` [PATCH v2 1/3] net/octeon_ep: optimize Rx and Tx routines Jerin Jacob
2023-12-06 17:24 ` [PATCH v3 " pbhagavatula
2023-12-06 17:24 ` [PATCH v3 2/3] net/octeon_ep: use SSE instructions for Rx routine pbhagavatula
2023-12-07 6:34 ` Jerin Jacob
2023-12-06 17:24 ` [PATCH v3 3/3] net/octeon_ep: use AVX2 instructions for Rx pbhagavatula
2023-12-07 6:49 ` [PATCH v4 1/3] net/octeon_ep: optimize Rx and Tx routines pbhagavatula
2023-12-07 6:49 ` [PATCH v4 2/3] net/octeon_ep: use SSE instructions for Rx routine pbhagavatula
2023-12-07 6:49 ` [PATCH v4 3/3] net/octeon_ep: use AVX2 instructions for Rx pbhagavatula
2023-12-11 12:05 ` Jerin Jacob [this message]
2023-12-11 13:43 ` [PATCH v5 1/3] net/octeon_ep: optimize Rx and Tx routines pbhagavatula
2023-12-11 13:43 ` [PATCH v5 2/3] net/octeon_ep: use SSE instructions for Rx routine pbhagavatula
2023-12-11 13:43 ` [PATCH v5 3/3] net/octeon_ep: use AVX2 instructions for Rx pbhagavatula
2023-12-12 5:29 ` Jerin Jacob
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=CALBAE1PLNKhNwxW8kfd6s6oK_551yYDPiTKS2Tr1GMALkWcaoQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=pbhagavatula@marvell.com \
--cc=vattunuru@marvell.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).