From: Stephen Hemminger <stephen@networkplumber.org>
To: okaya@kernel.org
Cc: Harman Kalra <hkalra@marvell.com>, dev@dpdk.org
Subject: Re: [PATCH v1 6/7] eal_interrupts: don't reinitialize threads
Date: Mon, 14 Aug 2023 19:20:40 -0700 [thread overview]
Message-ID: <20230814192040.2b81965f@hermes.local> (raw)
In-Reply-To: <20230815013826.1288972-7-okaya@kernel.org>
On Mon, 14 Aug 2023 21:38:25 -0400
okaya@kernel.org wrote:
> diff --git a/lib/eal/linux/eal_interrupts.c b/lib/eal/linux/eal_interrupts.c
> index d52ec8eb4c..aa296f153b 100644
> --- a/lib/eal/linux/eal_interrupts.c
> +++ b/lib/eal/linux/eal_interrupts.c
> @@ -1174,6 +1174,10 @@ int
> rte_eal_intr_init(void)
> {
> int ret = 0;
> + static int initialized = 0;
> +
> + if (initialized)
> + return 0;
>
> /* init the global interrupt source head */
> TAILQ_INIT(&intr_sources);
> @@ -1196,6 +1200,7 @@ rte_eal_intr_init(void)
> "Failed to create thread for interrupt handling\n");
> }
>
> + initialized = true;
If you want a bool, use a bool
next prev parent reply other threads:[~2023-08-15 2:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 1:38 [PATCH v1 0/7] support reinit flow okaya
2023-08-15 1:38 ` [PATCH v1 1/7] eal: fixes for re-initialization issues okaya
2023-08-15 2:21 ` Stephen Hemminger
2023-08-15 2:24 ` Stephen Hemminger
2023-08-15 1:38 ` [PATCH v1 2/7] tailq: skip init if already initialized okaya
2023-08-15 2:22 ` Stephen Hemminger
2023-08-15 1:38 ` [PATCH v1 3/7] eal_memzone: bail out on initialized okaya
2023-08-15 2:22 ` Stephen Hemminger
2023-08-15 1:38 ` [PATCH v1 4/7] memseg: init once okaya
2023-08-15 1:38 ` [PATCH v1 5/7] eal_memory: skip initialization okaya
2023-08-15 1:38 ` [PATCH v1 6/7] eal_interrupts: don't reinitialize threads okaya
2023-08-15 2:20 ` Stephen Hemminger [this message]
2023-08-15 1:38 ` [PATCH v1 7/7] eal: initialize worker threads once okaya
2023-08-15 2:24 ` Stephen Hemminger
2023-08-15 2:12 ` [PATCH v1 0/7] support reinit flow Stephen Hemminger
2023-08-15 3:12 ` Sinan Kaya
2023-08-15 21:49 ` Stephen Hemminger
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=20230814192040.2b81965f@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=okaya@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.