From: David Marchand <david.marchand@redhat.com>
To: "Varghese, Vipin" <Vipin.Varghese@amd.com>,
Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: DPDK Release Status Meeting
Date: Thu, 24 Nov 2022 13:38:21 +0100 [thread overview]
Message-ID: <CAJFAV8xB+bjvPqE7FhKTGU+5HFMMviQbpQmrubg-9k+yKkrs=w@mail.gmail.com> (raw)
In-Reply-To: <MN2PR12MB308577389FFC69878B4A01C4820F9@MN2PR12MB3085.namprd12.prod.outlook.com>
Hello,
On Thu, Nov 24, 2022 at 1:31 PM Varghese, Vipin <Vipin.Varghese@amd.com> wrote:
>
> Hi John and Thomas,
>
> Sharing an observation for compilation failure
Thanks for reporting.
I suspect you forgot to mention that this error is only seen with some
additional -DRTE_BBDEV_OFFLOAD_COST in cflags.
>
> Git head: 9cb8326456317264a7d085978634661c520af706
> Application – test-bbdev
> Error: ```
>
> ../app/test-bbdev/test_bbdev_perf.c: In function ‘get_bbdev_queue_stats’:
> ../app/test-bbdev/test_bbdev_perf.c:4936:16: error: ‘struct rte_bbdev_stats’ has no member named ‘enqueue_warning_count’; did you mean ‘enqueue_warn_count’?
> 4936 | stats->enqueue_warning_count = q_stats->enqueue_warning_count;
> | ^~~~~~~~~~~~~~~~~~~~~
> | enqueue_warn_count
> ../app/test-bbdev/test_bbdev_perf.c:4936:49: error: ‘struct rte_bbdev_stats’ has no member named ‘enqueue_warning_count’; did you mean ‘enqueue_warn_count’?
> 4936 | stats->enqueue_warning_count = q_stats->enqueue_warning_count;
> | ^~~~~~~~~~~~~~~~~~~~~
> | enqueue_warn_count
> ../app/test-bbdev/test_bbdev_perf.c:4937:16: error: ‘struct rte_bbdev_stats’ has no member named ‘dequeue_warning_count’; did you mean ‘dequeue_warn_count’?
> 4937 | stats->dequeue_warning_count = q_stats->dequeue_warning_count;
> | ^~~~~~~~~~~~~~~~~~~~~
> | dequeue_warn_count
> ../app/test-bbdev/test_bbdev_perf.c:4937:49: error: ‘struct rte_bbdev_stats’ has no member named ‘dequeue_warning_count’; did you mean ‘dequeue_warn_count’?
> 4937 | stats->dequeue_warning_count = q_stats->dequeue_warning_count;
> | ^~~~~~~~~~~~~~~~~~~~~
> | dequeue_warn_count
> ````
>
> Reason for error: rte_bbdev_stats has dequeue_warn_count
> Fix: convert stats to warn rather than warning
The fix should be trivial, can you send it quickly?
Thanks.
--
David Marchand
parent reply other threads:[~2022-11-24 12:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <MN2PR12MB308577389FFC69878B4A01C4820F9@MN2PR12MB3085.namprd12.prod.outlook.com>]
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='CAJFAV8xB+bjvPqE7FhKTGU+5HFMMviQbpQmrubg-9k+yKkrs=w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Vipin.Varghese@amd.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
/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).