From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com
Cc: hernan.vargas@intel.com, Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v1 0/3] bbdev: remove offload cost
Date: Wed, 14 Dec 2022 23:33:43 +0000 [thread overview]
Message-ID: <20221214233346.391973-1-nicolas.chautru@intel.com> (raw)
Removing the optional build flag RTE_BBDEV_OFFLOAD_COST
from Intel baseband PMDs and bbdev-test application.
This helps to simplify build variants complexity
causing compilation issues to be missed.
Maxime, the first commit is actually a miss related
to last commit on top of tree, you may want to merge
these two commits together in the history.
Sorry for missing it earlier.
Nicolas Chautru (3):
test/bbdev: explicit check for allocation failure
drivers/baseband: remove offload cost optional build flag
app/bbdev-test: remove offload cost optional build flag
app/test-bbdev/test_bbdev_perf.c | 29 +-------
drivers/baseband/acc/acc_common.h | 12 +---
drivers/baseband/acc/rte_acc100_pmd.c | 2 -
drivers/baseband/acc/rte_acc200_pmd.c | 2 -
.../fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 10 ---
drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 10 ---
.../baseband/turbo_sw/bbdev_turbo_software.c | 70 ++++---------------
7 files changed, 17 insertions(+), 118 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-14 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 23:33 Nicolas Chautru [this message]
2022-12-14 23:33 ` [PATCH v1 1/3] test/bbdev: explicit check for allocation failure Nicolas Chautru
2023-01-06 14:51 ` Maxime Coquelin
2023-01-06 15:37 ` Chautru, Nicolas
2023-01-10 8:32 ` Maxime Coquelin
2022-12-14 23:33 ` [PATCH v1 2/3] drivers/baseband: remove offload cost optional build flag Nicolas Chautru
2023-01-06 14:54 ` Maxime Coquelin
2022-12-14 23:33 ` [PATCH v1 3/3] app/bbdev-test: " Nicolas Chautru
2023-01-06 14:55 ` Maxime Coquelin
2023-01-03 22:07 ` [PATCH v1 0/3] bbdev: remove offload cost Chautru, Nicolas
2023-01-04 12:42 ` Maxime Coquelin
2023-01-04 18:01 ` Chautru, Nicolas
2023-01-05 9:53 ` Maxime Coquelin
2023-01-10 8:43 ` 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=20221214233346.391973-1-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=dev@dpdk.org \
--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).