From: okaya@kernel.org
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Sinan Kaya <okaya@kernel.org>
Subject: [PATCH v3 3/7] eal_memzone: bail out on initialized
Date: Mon, 14 Aug 2023 23:52:35 -0400 [thread overview]
Message-ID: <20230815035239.1365591-4-okaya@kernel.org> (raw)
In-Reply-To: <20230815035239.1365591-1-okaya@kernel.org>
From: Sinan Kaya <okaya@kernel.org>
Initialize memzone once and bail out if someone calls init
multiple times.
Signed-off-by: Sinan Kaya <okaya@kernel.org>
---
lib/eal/common/eal_common_memzone.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/lib/eal/common/eal_common_memzone.c b/lib/eal/common/eal_common_memzone.c
index 1f3e701499..6645ccfe83 100644
--- a/lib/eal/common/eal_common_memzone.c
+++ b/lib/eal/common/eal_common_memzone.c
@@ -22,6 +22,8 @@
#include "eal_private.h"
#include "eal_memcfg.h"
+static bool memzone_initialized;
+
/* Default count used until rte_memzone_max_set() is called */
#define DEFAULT_MAX_MEMZONE_COUNT 2560
@@ -426,6 +428,9 @@ rte_eal_memzone_init(void)
struct rte_mem_config *mcfg;
int ret = 0;
+ if (memzone_initialized)
+ return 0;
+
/* get pointer to global configuration */
mcfg = rte_eal_get_configuration()->mem_config;
@@ -444,6 +449,8 @@ rte_eal_memzone_init(void)
rte_rwlock_write_unlock(&mcfg->mlock);
+ memzone_initialized = true;
+
return ret;
}
--
2.25.1
next prev parent reply other threads:[~2023-08-15 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 3:52 [PATCH v3 0/7] support reinit flow okaya
2023-08-15 3:52 ` [PATCH v3 1/7] eal: fixes for re-initialization issues okaya
2023-08-15 3:52 ` [PATCH v3 2/7] tailq: skip init if already initialized okaya
2023-08-15 3:52 ` okaya [this message]
2023-08-15 3:52 ` [PATCH v3 4/7] memseg: init once okaya
2023-08-15 3:52 ` [PATCH v3 5/7] eal_memory: skip initialization okaya
2023-08-15 3:52 ` [PATCH v3 6/7] eal_interrupts: don't reinitialize threads okaya
2023-08-15 3:52 ` [PATCH v3 7/7] eal: initialize worker threads once okaya
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=20230815035239.1365591-4-okaya@kernel.org \
--to=okaya@kernel.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.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.