From: Yasin CANER <yasinncaner@gmail.com>
To: dev@dpdk.org
Cc: Yasin CANER <yasin.caner@ulakhaberlesme.com.tr>,
Olivier Matz <olivier.matz@6wind.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [PATCH] lib/mempool : rte_mempool_avail_count, fixing return bigger than mempool size
Date: Tue, 16 May 2023 13:41:46 +0000 [thread overview]
Message-ID: <20230516134146.480047-1-yasinncaner@gmail.com> (raw)
From: Yasin CANER <yasin.caner@ulakhaberlesme.com.tr>
after a while working rte_mempool_avail_count function returns bigger
than mempool size that cause miscalculation rte_mempool_in_use_count.
it helps to avoid miscalculation rte_mempool_in_use_count.
Bugzilla ID: 1229
Signed-off-by: Yasin CANER <yasin.caner@ulakhaberlesme.com.tr>
---
lib/mempool/rte_mempool.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/mempool/rte_mempool.c b/lib/mempool/rte_mempool.c
index cf5dea2304..17ed1eb845 100644
--- a/lib/mempool/rte_mempool.c
+++ b/lib/mempool/rte_mempool.c
@@ -1009,8 +1009,11 @@ rte_mempool_avail_count(const struct rte_mempool *mp)
count = rte_mempool_ops_get_count(mp);
- if (mp->cache_size == 0)
+ if (mp->cache_size == 0) {
+ if (count > mp->size)
+ return mp->size;
return count;
+ }
for (lcore_id = 0; lcore_id < RTE_MAX_LCORE; lcore_id++)
count += mp->local_cache[lcore_id].len;
--
2.25.1
next reply other threads:[~2023-05-16 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 13:41 Yasin CANER [this message]
2023-05-16 15:23 ` Stephen Hemminger
2023-05-16 16:03 ` Morten Brørup
2023-05-17 8:01 ` Yasin CANER
2023-05-17 8:38 ` Morten Brørup
2023-05-17 9:04 ` Morten Brørup
2023-05-17 11:37 ` Yasin CANER
2023-05-17 11:53 ` David Marchand
2023-05-17 12:23 ` Morten Brørup
2023-05-18 8:37 ` Yasin CANER
2023-05-18 8:53 ` Morten Brørup
2023-05-18 15:40 ` Mattias Rönnblom
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=20230516134146.480047-1-yasinncaner@gmail.com \
--to=yasinncaner@gmail.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=yasin.caner@ulakhaberlesme.com.tr \
/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).