DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] net/bnxt: vector mode patches
Date: Mon, 7 Jun 2021 14:36:53 -0700	[thread overview]
Message-ID: <CACZ4nhvEgG9WWeG6YMZ3AXSfHZ-Y-SgnK9QOwaRaEmeVFyNuyQ@mail.gmail.com> (raw)
In-Reply-To: <20210524185952.673258-1-lance.richardson@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

On Mon, May 24, 2021 at 12:00 PM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Vector mode updates for the bnxt PMD.
>
> Lance Richardson (3):
>   net/bnxt: refactor HW ptype mapping table
>   net/bnxt: fix Rx burst size constraint
>   net/bnxt: add AVX2 vector PMD

Patchset applied to dpdk-next-net-brcm/for-next-net branch.

>
>  doc/guides/nics/bnxt.rst              |  57 ++-
>  drivers/net/bnxt/bnxt_ethdev.c        | 119 +++--
>  drivers/net/bnxt/bnxt_rxr.c           |  38 +-
>  drivers/net/bnxt/bnxt_rxr.h           |  54 ++-
>  drivers/net/bnxt/bnxt_rxtx_vec_avx2.c | 597 ++++++++++++++++++++++++++
>  drivers/net/bnxt/bnxt_rxtx_vec_neon.c |  73 +++-
>  drivers/net/bnxt/bnxt_rxtx_vec_sse.c  |  78 ++--
>  drivers/net/bnxt/bnxt_txr.h           |   7 +
>  drivers/net/bnxt/meson.build          |  17 +
>  9 files changed, 911 insertions(+), 129 deletions(-)
>  create mode 100644 drivers/net/bnxt/bnxt_rxtx_vec_avx2.c
>
> --
> 2.25.1
>

      parent reply	other threads:[~2021-06-07 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 18:59 Lance Richardson
2021-05-24 18:59 ` [dpdk-dev] [PATCH 1/3] net/bnxt: refactor HW ptype mapping table Lance Richardson
2021-05-24 18:59 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix Rx burst size constraint Lance Richardson
2021-05-24 18:59 ` [dpdk-dev] [PATCH 3/3] net/bnxt: add AVX2 vector PMD Lance Richardson
2021-05-26 18:33   ` Lance Richardson
2021-06-07 21:36 ` Ajit Khaparde [this message]

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=CACZ4nhvEgG9WWeG6YMZ3AXSfHZ-Y-SgnK9QOwaRaEmeVFyNuyQ@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@broadcom.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).