From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] ethdev: rte_eth_rx_queue_count is a dataplane function
Date: Thu, 18 Aug 2022 13:23:40 +0100 [thread overview]
Message-ID: <f4d6fbd0-4c30-15cb-ace5-27212a435f7b@xilinx.com> (raw)
In-Reply-To: <20220818093744.76157-1-mb@smartsharesystems.com>
On 8/18/2022 10:37 AM, Morten Brørup wrote:
> Applications may use rte_eth_rx_queue_count() in the RX stage of the
> dataplane, so only check the function parameters if built with
> RTE_ETHDEV_DEBUG_RX.
>
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
I don't remember if those checks done by default intentionally, but I
don't think so,
And since other relevant functions do the same thing:
Acked-by: Ferruh Yigit <ferruh.yigit@xilinx.com>
next prev parent reply other threads:[~2022-08-18 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 9:37 Morten Brørup
2022-08-18 12:23 ` Ferruh Yigit [this message]
2022-09-12 14:47 ` Andrew Rybchenko
2022-09-22 13:46 ` Morten Brørup
2022-09-28 7:57 ` Andrew Rybchenko
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=f4d6fbd0-4c30-15cb-ace5-27212a435f7b@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).