From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: dev@dpdk.org
Subject: Re: [PATCH v1 2/2] app/bbdev: add support for interrupt disable
Date: Mon, 28 Oct 2024 15:08:05 +0530 [thread overview]
Message-ID: <eb895673-0d29-c390-7b15-9bbf24c02bc9@oss.nxp.com> (raw)
In-Reply-To: <20241025175709.1415722-3-nicolas.chautru@intel.com>
Reviewed-by: Hemant Agrawal <hemant.agrawal@nxp.com>
On 25-10-2024 23:27, Nicolas Chautru wrote:
> Adding support for calling the interrupt disable api
> for coverage.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> app/test-bbdev/test_bbdev_perf.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/app/test-bbdev/test_bbdev_perf.c b/app/test-bbdev/test_bbdev_perf.c
> index 405c22de44..6ee1ca34b2 100644
> --- a/app/test-bbdev/test_bbdev_perf.c
> +++ b/app/test-bbdev/test_bbdev_perf.c
> @@ -3535,6 +3535,10 @@ throughput_intr_lcore_ldpc_dec(void *arg)
> rte_atomic_store_explicit(&tp->nb_dequeued, 0, rte_memory_order_relaxed);
> }
>
> + TEST_ASSERT_SUCCESS(rte_bbdev_queue_intr_disable(tp->dev_id, queue_id),
> + "Failed to disable interrupts for dev: %u, queue_id: %u",
> + tp->dev_id, queue_id);
> +
> return TEST_SUCCESS;
> }
>
> @@ -3629,6 +3633,10 @@ throughput_intr_lcore_dec(void *arg)
> rte_atomic_store_explicit(&tp->nb_dequeued, 0, rte_memory_order_relaxed);
> }
>
> + TEST_ASSERT_SUCCESS(rte_bbdev_queue_intr_disable(tp->dev_id, queue_id),
> + "Failed to disable interrupts for dev: %u, queue_id: %u",
> + tp->dev_id, queue_id);
> +
> return TEST_SUCCESS;
> }
>
> @@ -3718,6 +3726,10 @@ throughput_intr_lcore_enc(void *arg)
> rte_atomic_store_explicit(&tp->nb_dequeued, 0, rte_memory_order_relaxed);
> }
>
> + TEST_ASSERT_SUCCESS(rte_bbdev_queue_intr_disable(tp->dev_id, queue_id),
> + "Failed to disable interrupts for dev: %u, queue_id: %u",
> + tp->dev_id, queue_id);
> +
> return TEST_SUCCESS;
> }
>
> @@ -3810,6 +3822,10 @@ throughput_intr_lcore_ldpc_enc(void *arg)
> rte_atomic_store_explicit(&tp->nb_dequeued, 0, rte_memory_order_relaxed);
> }
>
> + TEST_ASSERT_SUCCESS(rte_bbdev_queue_intr_disable(tp->dev_id, queue_id),
> + "Failed to disable interrupts for dev: %u, queue_id: %u",
> + tp->dev_id, queue_id);
> +
> return TEST_SUCCESS;
> }
>
> @@ -3901,6 +3917,10 @@ throughput_intr_lcore_fft(void *arg)
> rte_atomic_store_explicit(&tp->nb_dequeued, 0, rte_memory_order_relaxed);
> }
>
> + TEST_ASSERT_SUCCESS(rte_bbdev_queue_intr_disable(tp->dev_id, queue_id),
> + "Failed to disable interrupts for dev: %u, queue_id: %u",
> + tp->dev_id, queue_id);
> +
> return TEST_SUCCESS;
> }
>
> @@ -3986,6 +4006,10 @@ throughput_intr_lcore_mldts(void *arg)
> rte_atomic_store_explicit(&tp->nb_dequeued, 0, rte_memory_order_relaxed);
> }
>
> + TEST_ASSERT_SUCCESS(rte_bbdev_queue_intr_disable(tp->dev_id, queue_id),
> + "Failed to disable interrupts for dev: %u, queue_id: %u",
> + tp->dev_id, queue_id);
> +
> return TEST_SUCCESS;
> }
>
prev parent reply other threads:[~2024-10-28 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 17:57 [PATCH v1 0/2] app/bbdev: minor application updates Nicolas Chautru
2024-10-25 17:57 ` [PATCH v1 1/2] app/bbdev: add capture of queue dump Nicolas Chautru
2024-10-28 9:37 ` Hemant Agrawal
2024-10-25 17:57 ` [PATCH v1 2/2] app/bbdev: add support for interrupt disable Nicolas Chautru
2024-10-28 9:38 ` Hemant Agrawal [this message]
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=eb895673-0d29-c390-7b15-9bbf24c02bc9@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
/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).