DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, maxime.coquelin@redhat.com
Cc: trix@redhat.com, mdr@ashroe.eu, bruce.richardson@intel.com,
	hemant.agrawal@nxp.com, david.marchand@redhat.com,
	stephen@networkplumber.org, hernan.vargas@intel.com,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v13 0/1] bbdev-test extension
Date: Thu, 13 Oct 2022 19:17:53 -0700	[thread overview]
Message-ID: <20221014021754.48157-1-nicolas.chautru@intel.com> (raw)

v13: Leftover commit 16 from the acc200 series (introduced in v10).
     Updated the commit message and documentation incl. rel notes
     and bbdev-test one suggested by Maxime.
     Modification of vector used. Thanks.
    
v12: Rebase between commits notably to avoid interim build issue and test
     vector format issue raised by Akhil. Thanks.
v11: Fixed clang compilation error introduced in v10 16/16. Thanks
v10: Update of patch 13 to expose a single configuration API for the ACC devices.
     New commit 15 to refactor PMD code using helper functions for the descriptor
     index management and improve readability.
     New commit 16 to extend bbdev-test capability to support new
     operations and capabilities in the new PMD.
     Formatting fixes. Note that the checkpatch warning are False-Alarms.
     Thanks
v9: I had missed a compilation error in debug mode. 
v8: Rebased to latest and fixed related compilation error. Added acc200.ini and updated rel_notes.
    Formatting improvement in comments, docs and commit message.
v7: Additional update in commits 9,10,11 based on review from Maxime.
v5/v6:Updates based on Maxime reviews of v4/v5. Thanks.
v4: Rebase suggested by Maxime to split first commit and update the order within the series. No functional change. 
v3: Putting together ACC100 and ACC200 PMDs in common acc directory based on previous discussion on v2. 
v2: Includes now code refactory to have common structures and code reused with the parallel ACC1XX serie PMD which can be shared moving forward.
v1: This is targeting 22.11 and includes the PMD for the new serie integrated accelerator on Intel Xeon SPR-EEC.

Nic Chautru (1):
  test-bbdev: unit test extension including for FFT

 app/test-bbdev/test_bbdev_perf.c            | 540 +++++++++++-
 app/test-bbdev/test_bbdev_vector.c          | 182 ++++
 app/test-bbdev/test_bbdev_vector.h          |   1 +
 app/test-bbdev/test_vectors/fft_9.data      | 870 ++++++++++++++++++++
 app/test-bbdev/test_vectors/fft_byp_28.data | 102 +++
 doc/guides/rel_notes/release_22_11.rst      |   6 +
 doc/guides/tools/testbbdev.rst              | 133 +++
 7 files changed, 1817 insertions(+), 17 deletions(-)
 create mode 100644 app/test-bbdev/test_vectors/fft_9.data
 create mode 100644 app/test-bbdev/test_vectors/fft_byp_28.data

-- 
2.37.1


             reply	other threads:[~2022-10-14  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  2:17 Nicolas Chautru [this message]
2022-10-14  2:17 ` [PATCH v13 1/1] test-bbdev: unit test extension including for FFT Nicolas Chautru
2022-10-21 15:19   ` [EXT] " Akhil Goyal

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=20221014021754.48157-1-nicolas.chautru@intel.com \
    --to=nicolas.chautru@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdr@ashroe.eu \
    --cc=stephen@networkplumber.org \
    --cc=trix@redhat.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).