DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Hernan Vargas <hernan.vargas@intel.com>,
	dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com
Subject: Re: [PATCH v1 03/11] test/bbdev: rename macros from acc200 to vrb
Date: Tue, 17 Oct 2023 21:30:05 +0200	[thread overview]
Message-ID: <210bde74-ce62-4f53-ad59-e85914118349@redhat.com> (raw)
In-Reply-To: <20230929181328.104311-4-hernan.vargas@intel.com>



On 9/29/23 20:13, Hernan Vargas wrote:
> Renaming ACC200 macros to use generic intel vRAN Boost (VRB).
> No functional impact.
> 
> Signed-off-by: Hernan Vargas <hernan.vargas@intel.com>
> ---
>   app/test-bbdev/test_bbdev_perf.c | 91 ++++++++++++++++----------------
>   1 file changed, 45 insertions(+), 46 deletions(-)
> 
> diff --git a/app/test-bbdev/test_bbdev_perf.c b/app/test-bbdev/test_bbdev_perf.c
> index faea26c10eed..d4c001de0093 100644
> --- a/app/test-bbdev/test_bbdev_perf.c
> +++ b/app/test-bbdev/test_bbdev_perf.c
> @@ -64,14 +64,14 @@
>   #define ACC100_QMGR_INVALID_IDX -1
>   #define ACC100_QMGR_RR 1
>   #define ACC100_QOS_GBR 0
> -#define ACC200PF_DRIVER_NAME   ("intel_acc200_pf")
> -#define ACC200VF_DRIVER_NAME   ("intel_acc200_vf")
> -#define ACC200_QMGR_NUM_AQS 16
> -#define ACC200_QMGR_NUM_QGS 2
> -#define ACC200_QMGR_AQ_DEPTH 5
> -#define ACC200_QMGR_INVALID_IDX -1
> -#define ACC200_QMGR_RR 1
> -#define ACC200_QOS_GBR 0
> +#define VRBPF_DRIVER_NAME   ("intel_vran_boost_pf")
> +#define VRBVF_DRIVER_NAME   ("intel_vran_boost_vf")

Should it be a fix, since the driver name changed in an earlier version?


  reply	other threads:[~2023-10-17 19:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 18:13 [PATCH v1 00/11] test-bbdev changes for 23.11 Hernan Vargas
2023-09-29 18:13 ` [PATCH v1 01/11] test/bbdev: fix python script subprocess Hernan Vargas
2023-10-17 19:05   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 02/11] test/bbdev: update python script parameters Hernan Vargas
2023-10-17 19:07   ` Maxime Coquelin
2023-10-19  9:01     ` Chautru, Nicolas
2023-10-19  9:19       ` Maxime Coquelin
2023-10-19 12:09         ` Chautru, Nicolas
2023-10-19 12:20           ` Maxime Coquelin
2023-10-27 20:02           ` Chautru, Nicolas
2023-11-02 17:00             ` Maxime Coquelin
2023-11-02 18:18               ` Chautru, Nicolas
2023-11-03  9:48                 ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 03/11] test/bbdev: rename macros from acc200 to vrb Hernan Vargas
2023-10-17 19:30   ` Maxime Coquelin [this message]
2023-09-29 18:13 ` [PATCH v1 04/11] test/bbdev: handle exception for LLR generation Hernan Vargas
2023-10-17 19:30   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 05/11] test/bbdev: improve test log messages Hernan Vargas
2023-10-17 19:40   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 06/11] test/bbdev: assert failed test for queue configure Hernan Vargas
2023-10-17 19:43   ` Maxime Coquelin
2023-10-19  8:41     ` Chautru, Nicolas
2023-10-19  8:47       ` Maxime Coquelin
2023-10-19 12:12         ` Chautru, Nicolas
2023-10-23  9:05           ` Maxime Coquelin
2023-10-23  9:07             ` Maxime Coquelin
2023-10-23 15:10               ` Kevin Traynor
2023-09-29 18:13 ` [PATCH v1 07/11] test/bbdev: ldpc encoder concatenation vector Hernan Vargas
2023-10-17 19:44   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 08/11] test/bbdev: increase max burst size Hernan Vargas
2023-10-17 19:45   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 09/11] test/bbdev: add MLD support Hernan Vargas
2023-10-17 20:03   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 10/11] test/bbdev: support new FFT capabilities Hernan Vargas
2023-10-17 20:06   ` Maxime Coquelin
2023-09-29 18:13 ` [PATCH v1 11/11] test/bbdev: support 4 bit LLR compression Hernan Vargas
2023-10-17 20:08   ` 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=210bde74-ce62-4f53-ad59-e85914118349@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hernan.vargas@intel.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).