From: Hernan Vargas <hernan.vargas@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com,
Hernan Vargas <hernan.vargas@intel.com>
Subject: [PATCH v2 0/5] baseband/fpga_5gnr: maintenance changes to fpga_5gnr PMD
Date: Thu, 19 May 2022 22:05:51 -0500 [thread overview]
Message-ID: <20220520030556.3475133-1-hernan.vargas@intel.com> (raw)
Few PMD changes as part of maintenance of the driver. These are not required on the stable variants. Aiming to upstream these in 22.07.
Updated with review suggestions.
Hernan (5):
baseband/fpga_5gnr_fec: remove FLR timeout
baseband/fpga_5gnr_fec: add FPGA Mutex
baseband/fpga_5gnr_fec: add check for HARQ input length
baseband/fpga_5gnr_fec: enable validate LDPC enc/dec
baseband/fpga_5gnr_fec: remove filler from HARQ
app/test-bbdev/test_bbdev_perf.c | 4 -
.../baseband/fpga_5gnr_fec/fpga_5gnr_fec.h | 9 +-
.../fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 581 ++++++++++++++----
.../fpga_5gnr_fec/rte_pmd_fpga_5gnr_fec.h | 2 -
4 files changed, 451 insertions(+), 145 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-20 3:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 3:05 Hernan Vargas [this message]
2022-05-20 3:05 ` [PATCH v2 1/5] baseband/fpga_5gnr_fec: remove FLR timeout Hernan Vargas
2022-05-20 3:05 ` [PATCH v2 2/5] baseband/fpga_5gnr_fec: add FPGA Mutex Hernan Vargas
2022-05-20 3:05 ` [PATCH v2 3/5] baseband/fpga_5gnr_fec: add check for HARQ input length Hernan Vargas
2022-05-20 3:05 ` [PATCH v2 4/5] baseband/fpga_5gnr_fec: enable validate LDPC enc/dec Hernan Vargas
2022-05-20 3:05 ` [PATCH v2 5/5] baseband/fpga_5gnr_fec: remove filler from HARQ Hernan Vargas
2022-05-24 0:21 ` Chautru, Nicolas
2022-05-31 18:06 ` [EXT] [PATCH v2 0/5] baseband/fpga_5gnr: maintenance changes to fpga_5gnr PMD Akhil Goyal
2022-05-31 18:12 ` Chautru, Nicolas
2022-05-31 18:17 ` Akhil Goyal
2022-05-31 18:30 ` 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=20220520030556.3475133-1-hernan.vargas@intel.com \
--to=hernan.vargas@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=nicolas.chautru@intel.com \
--cc=qi.z.zhang@intel.com \
--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).