From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Tom Rix <trix@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v5 7/7] app/bbdev: update offload test to dequeue full ring
Date: Mon, 26 Oct 2020 16:27:21 +0000 [thread overview]
Message-ID: <BY5PR11MB4451E6436B6D029EDF58775DF8190@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2740f83e-d995-3b8b-2536-bec618c35d1e@redhat.com>
> -----Original Message-----
> From: Tom Rix <trix@redhat.com>
> Sent: Monday, October 26, 2020 6:56 AM
> To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org;
> akhil.goyal@nxp.com
> Cc: david.marchand@redhat.com
> Subject: Re: [PATCH v5 7/7] app/bbdev: update offload test to dequeue full
> ring
>
>
> On 10/23/20 4:43 PM, Nicolas Chautru wrote:
> > update offload dequeue to retrieve the full ring to be agnostic of
> > implementation.
> >
> > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > Acked-by: Aidan Goddard <aidan.goddard@accelercomm.com>
> > Acked-by: Dave Burley <dave.burley@accelercomm.com>
> > ---
> > app/test-bbdev/test_bbdev_perf.c | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/app/test-bbdev/test_bbdev_perf.c
> > b/app/test-bbdev/test_bbdev_perf.c
> > index b5dc536..a6884c5 100644
> > --- a/app/test-bbdev/test_bbdev_perf.c
> > +++ b/app/test-bbdev/test_bbdev_perf.c
> > @@ -4463,8 +4463,8 @@ typedef int (test_case_function)(struct
> active_device *ad,
> > /* Dequeue one operation */
> This comment and similar need to change, not doing just 1 anymore
We still just need one operation dequeued to be considered done.
> > do {
> > deq += rte_bbdev_dequeue_dec_ops(dev_id,
> queue_id,
> > - &ops_deq[deq], 1);
> > - } while (unlikely(deq != 1));
> > + &ops_deq[deq], enq);
> > + } while (unlikely(deq == 0));
>
> This check looks wrong, should likely be (deq != enq)
>
> Similar below
No that is intentional. Not waiting for everything to be done but purely the first dequeue. If not this would be run multiple times.
The rest of ring is dequeued below.
>
> Tom
>
> >
> > deq_last_time = rte_rdtsc_precise() - deq_start_time;
> > time_st->deq_max_time = RTE_MAX(time_st-
> >deq_max_time, @@ -4554,8
> > +4554,8 @@ typedef int (test_case_function)(struct active_device *ad,
> > /* Dequeue one operation */
> > do {
> > deq += rte_bbdev_dequeue_ldpc_dec_ops(dev_id,
> queue_id,
> > - &ops_deq[deq], 1);
> > - } while (unlikely(deq != 1));
> > + &ops_deq[deq], enq);
> > + } while (unlikely(deq == 0));
> >
> > deq_last_time = rte_rdtsc_precise() - deq_start_time;
> > time_st->deq_max_time = RTE_MAX(time_st-
> >deq_max_time, @@ -4642,8
> > +4642,8 @@ typedef int (test_case_function)(struct active_device *ad,
> > /* Dequeue one operation */
> > do {
> > deq += rte_bbdev_dequeue_enc_ops(dev_id,
> queue_id,
> > - &ops_deq[deq], 1);
> > - } while (unlikely(deq != 1));
> > + &ops_deq[deq], enq);
> > + } while (unlikely(deq == 0));
> >
> > deq_last_time = rte_rdtsc_precise() - deq_start_time;
> > time_st->deq_max_time = RTE_MAX(time_st-
> >deq_max_time, @@ -4725,8
> > +4725,8 @@ typedef int (test_case_function)(struct active_device *ad,
> > /* Dequeue one operation */
> > do {
> > deq += rte_bbdev_dequeue_ldpc_enc_ops(dev_id,
> queue_id,
> > - &ops_deq[deq], 1);
> > - } while (unlikely(deq != 1));
> > + &ops_deq[deq], enq);
> > + } while (unlikely(deq == 0));
> >
> > deq_last_time = rte_rdtsc_precise() - deq_start_time;
> > time_st->deq_max_time = RTE_MAX(time_st-
> >deq_max_time,
next prev parent reply other threads:[~2020-10-26 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 23:42 [dpdk-dev] [PATCH v5 0/7] BBDEV test updates Nicolas Chautru
2020-10-23 23:42 ` [dpdk-dev] [PATCH v5 1/7] app/bbdev: add explicit ut for latency vs validation Nicolas Chautru
2020-10-26 12:55 ` Tom Rix
2020-10-26 17:30 ` Chautru, Nicolas
2020-10-28 20:37 ` Tom Rix
2020-10-23 23:42 ` [dpdk-dev] [PATCH v5 2/7] app/bbdev: add explicit check for counters Nicolas Chautru
2020-10-26 13:05 ` Tom Rix
2020-10-26 16:29 ` Chautru, Nicolas
2020-10-28 20:31 ` Tom Rix
2020-10-23 23:42 ` [dpdk-dev] [PATCH v5 3/7] app/bbdev: include explicit HARQ preloading Nicolas Chautru
2020-10-26 13:31 ` Tom Rix
2020-10-26 16:50 ` Chautru, Nicolas
2020-10-28 20:33 ` Tom Rix
2020-10-23 23:42 ` [dpdk-dev] [PATCH v5 4/7] app/bbdev: define wait for offload Nicolas Chautru
2020-10-26 13:33 ` Tom Rix
2020-10-26 16:04 ` Chautru, Nicolas
2020-10-28 20:24 ` Tom Rix
2020-10-23 23:42 ` [dpdk-dev] [PATCH v5 5/7] app/bbdev: skip bler ut when compression is used Nicolas Chautru
2020-10-26 13:35 ` Tom Rix
2020-10-23 23:43 ` [dpdk-dev] [PATCH v5 6/7] app/bbdev: reduce duration of throughput test Nicolas Chautru
2020-10-26 13:39 ` Tom Rix
2020-10-23 23:43 ` [dpdk-dev] [PATCH v5 7/7] app/bbdev: update offload test to dequeue full ring Nicolas Chautru
2020-10-26 13:55 ` Tom Rix
2020-10-26 16:27 ` Chautru, Nicolas [this message]
2020-10-28 20:28 ` Tom Rix
2020-10-24 7:47 ` [dpdk-dev] [PATCH v5 0/7] BBDEV test updates David Marchand
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=BY5PR11MB4451E6436B6D029EDF58775DF8190@BY5PR11MB4451.namprd11.prod.outlook.com \
--to=nicolas.chautru@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).