From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ed Czeck <ed.czeck@atomicrules.com>, dev@dpdk.org
Cc: john.miller@atomicrules.com, shepard.siegel@atomicrules.com
Subject: Re: [dpdk-dev] [PATCH 1/3] net/ark: add recovery code for lack of mbufs during runtime
Date: Tue, 9 Oct 2018 16:57:45 +0100 [thread overview]
Message-ID: <f97994b6-b392-7d92-0731-1771c586aa88@intel.com> (raw)
In-Reply-To: <1539033410-21422-1-git-send-email-ed.czeck@atomicrules.com>
On 10/8/2018 10:16 PM, Ed Czeck wrote:
> Fail with rte_exit() when the lack of mbufs is not recoverable.
>
> Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com>
<...>
> @@ -495,6 +508,33 @@ eth_ark_rx_seed_mbufs(struct ark_rx_queue *queue)
> return 0;
> }
>
> +int
> +eth_ark_rx_seed_recovery(struct ark_rx_queue *queue,
> + uint32_t *pnb,
> + struct rte_mbuf **mbufs)
> +{
> + int status = -1;
> +
> + /* Ignore small allocation failures */
> + if (*pnb <= 64)
> + return -1;
> +
> + *pnb = 64U;
> + status = rte_pktmbuf_alloc_bulk(queue->mb_pool, mbufs, *pnb);
> + if (status != 0) {
> + PMD_DRV_LOG(ERR,
> + "ARK: Could not allocate %u mbufs from pool for RX queue %u;"
> + " %u free buffers remaining in queue\n",
> + *pnb, queue->queue_index,
> + queue->seed_index - queue->cons_index);
> + if (queue->seed_index - queue->cons_index < 64) {
> + rte_exit(EXIT_FAILURE,
> + "ARK: No mbufs in pool; do you have a leak?\n");
Hi Ed,
We are trying to get rid of rte_exit() calls, reasoning is DPDK is a library and
application should decide to exit or not, and a DPDK application may be using
multiple NICs/libraries/functionalities, failure in one of them should not cause
all application to exit.
Can you please replace rte_exit() usage?
next prev parent reply other threads:[~2018-10-09 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 21:16 Ed Czeck
2018-10-08 21:16 ` [dpdk-dev] [PATCH 2/3] net/ark: remove useless hardware notifications Ed Czeck
2018-10-15 12:53 ` [dpdk-dev] [PATCH v2 " Ed Czeck
2018-10-08 21:16 ` [dpdk-dev] [PATCH 3/3] net/ark: support for updated Tx hardware with user meta data Ed Czeck
2018-10-09 15:59 ` Ferruh Yigit
2018-10-15 12:53 ` [dpdk-dev] [PATCH v2 3/3] net/ark: support for updated hardware and Tx " Ed Czeck
2018-10-09 15:57 ` Ferruh Yigit [this message]
2018-10-15 12:52 ` [dpdk-dev] [PATCH v2 1/3] net/ark: add recovery code for lack of mbufs during runtime Ed Czeck
2018-10-15 14:09 ` 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=f97994b6-b392-7d92-0731-1771c586aa88@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).