DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hernan Vargas <hernan.vargas@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com,
	maxime.coquelin@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com,
	Hernan Vargas <hernan.vargas@intel.com>
Subject: [PATCH v3 00/12] acc baseband PMD fix and updates for 24.11
Date: Wed,  9 Oct 2024 14:12:50 -0700	[thread overview]
Message-ID: <20241009211302.177471-1-hernan.vargas@intel.com> (raw)

This series targets 24.11.
v3: Updated code with community recommendations. Added 2 commits for rte_free refactor and clean up of VRB1 capabilities.
v2: Rebased to the latest next-baseband-for-main which includes needed rte_bbdev lib updates.
v1: It includes a memory access fix, refactoring of queue allocation and general improvements.

Hernan Vargas (12):
  baseband/acc: fix access to deallocated mem
  baseband/acc: fix soft output bypass RM
  baseband/acc: queue allocation refactor
  baseband/acc: configure max queues per device
  baseband/acc: future proof structure comparison
  baseband/acc: enhance SW ring alignment
  baseband/acc: algorithm tuning for LDPC decoder
  baseband/acc: remove check on HARQ memory
  baseband/acc: reset ring data valid bit
  baseband/acc: cosmetic changes
  baseband/acc: rte free refactor
  baseband/acc: clean up of VRB1 capabilities

 doc/guides/bbdevs/vrb1.rst            |   3 -
 drivers/baseband/acc/acc_common.h     |  16 +-
 drivers/baseband/acc/rte_acc100_pmd.c |  61 ++---
 drivers/baseband/acc/rte_vrb_pmd.c    | 335 ++++++++++++++++----------
 4 files changed, 227 insertions(+), 188 deletions(-)

-- 
2.37.1


             reply	other threads:[~2024-10-09 21:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 21:12 Hernan Vargas [this message]
2024-10-09 21:12 ` [PATCH v3 01/12] baseband/acc: fix access to deallocated mem Hernan Vargas
2024-10-09 21:12 ` [PATCH v3 02/12] baseband/acc: fix soft output bypass RM Hernan Vargas
2024-10-14  9:47   ` Maxime Coquelin
2024-10-09 21:12 ` [PATCH v3 03/12] baseband/acc: queue allocation refactor Hernan Vargas
2024-10-14  9:49   ` Maxime Coquelin
2024-10-09 21:12 ` [PATCH v3 04/12] baseband/acc: configure max queues per device Hernan Vargas
2024-10-09 21:12 ` [PATCH v3 05/12] baseband/acc: future proof structure comparison Hernan Vargas
2024-10-09 21:12 ` [PATCH v3 06/12] baseband/acc: enhance SW ring alignment Hernan Vargas
2024-10-14 11:01   ` Maxime Coquelin
2024-10-09 21:12 ` [PATCH v3 07/12] baseband/acc: algorithm tuning for LDPC decoder Hernan Vargas
2024-10-09 21:12 ` [PATCH v3 08/12] baseband/acc: remove check on HARQ memory Hernan Vargas
2024-10-09 21:12 ` [PATCH v3 09/12] baseband/acc: reset ring data valid bit Hernan Vargas
2024-10-09 21:13 ` [PATCH v3 10/12] baseband/acc: cosmetic changes Hernan Vargas
2024-10-14 11:02   ` Maxime Coquelin
2024-10-09 21:13 ` [PATCH v3 11/12] baseband/acc: rte free refactor Hernan Vargas
2024-10-14 11:03   ` Maxime Coquelin
2024-10-09 21:13 ` [PATCH v3 12/12] baseband/acc: clean up of VRB1 capabilities Hernan Vargas
2024-10-14 11:04   ` Maxime Coquelin
2024-10-14 11:43 ` [PATCH v3 00/12] acc baseband PMD fix and updates for 24.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=20241009211302.177471-1-hernan.vargas@intel.com \
    --to=hernan.vargas@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=maxime.coquelin@redhat.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).