From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com,
ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru,
bingz@nvidia.com, Xiaoyun Li <xiaoyun.li@intel.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: warn only once for badly behaving applications
Date: Tue, 26 Oct 2021 17:56:58 +0200 [thread overview]
Message-ID: <3415992.2jfn0xn0IN@thomas> (raw)
In-Reply-To: <20211026145851.21944-1-david.marchand@redhat.com>
26/10/2021 16:58, David Marchand:
> Warning continuously is a pain when developping or if a unit test
> is/gets broken.
>
> It could also be a problem if application behaves badly only in some
> corner cases and a DoS results of those logs being continuously displayed.
>
> Let's warn once per port and per rx/tx.
>
> Getting such a log is scary, but let's make it more eye catching by
> dumping a backtrace with it.
[...]
> Fixes: c87d435a4d79 ("ethdev: copy fast-path API into separate structure")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
[...]
> +static struct dummy_queue *dummy_queues_ref[RTE_MAX_ETHPORTS][RTE_MAX_QUEUES_PER_PORT];
> +static struct dummy_queue dummy_queues[RTE_MAX_ETHPORTS];
I feel we could better name those arrays, maybe adding a comment.
First one is really queues array while the second one is to share
the same value with all queues of a port. Right?
> +RTE_INIT(dummy_queue_init)
> +{
> + uint16_t port_id;
> +
> + for (port_id = 0; port_id < RTE_DIM(dummy_queues); port_id++) {
> + unsigned int i;
q would be a better name than i
> +
> + for (i = 0; i < RTE_DIM(dummy_queues_ref[port_id]); i++)
> + dummy_queues_ref[port_id][i] = &dummy_queues[port_id];
> + }
> +}
> +
> static uint16_t
> -dummy_eth_rx_burst(__rte_unused void *rxq,
> +dummy_eth_rx_burst(void *rxq,
> __rte_unused struct rte_mbuf **rx_pkts,
> __rte_unused uint16_t nb_pkts)
> {
> - RTE_ETHDEV_LOG(ERR, "rx_pkt_burst for not ready port\n");
> + struct dummy_queue *q = rxq;
> +
> + if (!q->rx_warn_once) {
> + uint16_t port_id = q - dummy_queues;
> +
> + RTE_ETHDEV_LOG(ERR, "lcore %u called rx_pkt_burst for not ready port %"PRIu16"\n",
> + rte_lcore_id(), port_id);
> + rte_dump_stack();
> + q->rx_warn_once = true;
> + }
> rte_errno = ENOTSUP;
> return 0;
> }
OK with this log.
[...]
> eth_dev_fp_ops_reset(struct rte_eth_fp_ops *fpo)
> {
> static void *dummy_data[RTE_MAX_QUEUES_PER_PORT];
> - static const struct rte_eth_fp_ops dummy_ops = {
> + uint16_t port_id = fpo - rte_eth_fp_ops;
> +
> + dummy_queues[port_id].rx_warn_once = false;
> + dummy_queues[port_id].tx_warn_once = false;
> + *fpo = (struct rte_eth_fp_ops) {
> .rx_pkt_burst = dummy_eth_rx_burst,
> .tx_pkt_burst = dummy_eth_tx_burst,
> - .rxq = {.data = dummy_data, .clbk = dummy_data,},
> - .txq = {.data = dummy_data, .clbk = dummy_data,},
> + .rxq = (struct rte_ethdev_qdata) {
Why this cast? rte_eth_fp_ops.rxq is of type rte_ethdev_qdata.
> + .data = (void **)&dummy_queues_ref[port_id],
> + .clbk = dummy_data,
> + },
> + .txq = (struct rte_ethdev_qdata) {
> + .data = (void **)&dummy_queues_ref[port_id],
> + .clbk = dummy_data,
> + },
> };
> -
> - *fpo = dummy_ops;
> }
next prev parent reply other threads:[~2021-10-26 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:58 David Marchand
2021-10-26 15:56 ` Thomas Monjalon [this message]
2021-10-27 7:20 ` David Marchand
2021-10-27 8:16 ` Olivier Matz
2021-10-27 8:42 ` David Marchand
2021-10-26 17:10 ` Ananyev, Konstantin
2021-10-27 7:23 ` David Marchand
2021-10-27 12:01 ` [dpdk-dev] [PATCH v2] ethdev: warn once for buggy applications David Marchand
2021-10-27 12:15 ` Ananyev, Konstantin
2021-10-27 12:46 ` Thomas Monjalon
2021-10-27 17:31 ` Ferruh Yigit
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=3415992.2jfn0xn0IN@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bingz@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=xiaoyun.li@intel.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).