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,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v2 0/2] doc/guides: bbdev clean up
Date: Fri, 13 Oct 2023 21:42:36 +0000 [thread overview]
Message-ID: <20231013214238.902741-1-nicolas.chautru@intel.com> (raw)
v2: adding extra commit to refer to bbdev test doc from each PMD
and avoid duplication.
Adding more information in bbdev documentation related to the
bbdev device discovery from info_get which was not very verbose so far.
Notably for FEC and FFT operations which have extra parameters to
manage different implementation variants.
Also use code snippet to refer to info structure and keep the doc
in sync moving forward.
Nicolas Chautru (2):
doc: bbdev device discovery clarification
doc/guides: refer to generic bbdev test section
doc/guides/bbdevs/acc100.rst | 33 ++--------------
doc/guides/bbdevs/fpga_5gnr_fec.rst | 39 ++-----------------
doc/guides/bbdevs/fpga_lte_fec.rst | 40 ++-----------------
doc/guides/bbdevs/la12xx.rst | 32 ++-------------
doc/guides/bbdevs/vrb1.rst | 36 ++---------------
doc/guides/bbdevs/vrb2.rst | 36 ++---------------
doc/guides/prog_guide/bbdev.rst | 60 ++++++++++++++++++++++++-----
doc/guides/tools/testbbdev.rst | 2 +
lib/bbdev/rte_bbdev.h | 6 +++
9 files changed, 79 insertions(+), 205 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-13 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 21:42 Nicolas Chautru [this message]
2023-10-13 21:42 ` [PATCH v2 1/2] doc: bbdev device discovery clarification Nicolas Chautru
2023-10-23 9:21 ` Maxime Coquelin
2023-10-13 21:42 ` [PATCH v2 2/2] doc/guides: refer to generic bbdev test section Nicolas Chautru
2023-10-23 9:23 ` 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=20231013214238.902741-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 \
/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).