DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com
Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com,
	hernan.vargas@intel.com, stable@dpdk.org,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v3 00/10] test-bbdev changes for 23.11
Date: Fri,  3 Nov 2023 23:34:03 +0000	[thread overview]
Message-ID: <20231103233413.756110-1-nicolas.chautru@intel.com> (raw)

v3: python script argument fix marked as deprecation first, with
    formal fix in following release.
    Maxime let me know if you want to something more formal in the
    release notes to call it out, currently embedded in script and
    commit message.
    typo correction.
v2: adding fixes for some of the commits requested by Maxime.

Update test-bbdev for 23.11.

Hernan Vargas (8):
  test/bbdev: fix python script subprocess
  test/bbdev: handle exception for LLR generation
  test/bbdev: improve test log messages
  test/bbdev: assert failed test for queue configure
  test/bbdev: ldpc encoder concatenation vector
  test/bbdev: add MLD support
  test/bbdev: support new FFT capabilities
  test/bbdev: support 4 bit LLR compression

Nicolas Chautru (2):
  test/bbdev: rename macros from acc200 to vrb
  test/bbdev: update python script parameters

 app/test-bbdev/main.c              |   3 +-
 app/test-bbdev/test-bbdev.py       |  55 ++-
 app/test-bbdev/test_bbdev.c        |   3 +-
 app/test-bbdev/test_bbdev_perf.c   | 673 ++++++++++++++++++++++++++---
 app/test-bbdev/test_bbdev_vector.c | 199 ++++++++-
 app/test-bbdev/test_bbdev_vector.h |   1 +
 6 files changed, 843 insertions(+), 91 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-11-03 23:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 23:34 Nicolas Chautru [this message]
2023-11-03 23:34 ` [PATCH v3 01/10] test/bbdev: fix python script subprocess Nicolas Chautru
2023-11-09 12:37   ` Maxime Coquelin
2023-11-03 23:34 ` [PATCH v3 02/10] test/bbdev: rename macros from acc200 to vrb Nicolas Chautru
2023-11-09 12:37   ` Maxime Coquelin
2023-11-03 23:34 ` [PATCH v3 03/10] test/bbdev: handle exception for LLR generation Nicolas Chautru
2023-11-09 12:46   ` Maxime Coquelin
2023-11-03 23:34 ` [PATCH v3 04/10] test/bbdev: improve test log messages Nicolas Chautru
2023-11-03 23:34 ` [PATCH v3 05/10] test/bbdev: assert failed test for queue configure Nicolas Chautru
2023-11-03 23:34 ` [PATCH v3 06/10] test/bbdev: ldpc encoder concatenation vector Nicolas Chautru
2023-11-03 23:34 ` [PATCH v3 07/10] test/bbdev: add MLD support Nicolas Chautru
2023-11-09 15:44   ` Maxime Coquelin
2023-11-03 23:34 ` [PATCH v3 08/10] test/bbdev: support new FFT capabilities Nicolas Chautru
2023-11-03 23:34 ` [PATCH v3 09/10] test/bbdev: support 4 bit LLR compression Nicolas Chautru
2023-11-03 23:34 ` [PATCH v3 10/10] test/bbdev: update python script parameters Nicolas Chautru
2023-11-09 10:16   ` Maxime Coquelin
2023-11-09 15:37     ` Chautru, Nicolas
2023-11-09 15:51 ` [PATCH v3 00/10] test-bbdev changes for 23.11 Maxime Coquelin

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=20231103233413.756110-1-nicolas.chautru@intel.com \
    --to=nicolas.chautru@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    /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).