DPDK usage discussions
 help / color / mirror / Atom feed
From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] rte_mempool_get returning null
Date: Wed, 30 Jun 2021 15:50:43 +0200
Message-ID: <26c96412-1f06-2ad5-6d0e-00a8125dc81e@filipjaniszewski.com> (raw)


What would be the reason for rte_mempool_get returning null even if
rte_mempool_avail_count returns a big positive number? I know is
positive since I've added a print in my code to test that..

I've a strange issue where once I extract N items from the pool (where N
is the exact size of the pool) then the rte_mempool_get fails even if in
between the N extraction I've replenished the pool with rte_mempool_put
so that rte_mempool_avail_count is always positive.

The pool is created like this:

    data_pool_ = rte_mempool_create(
                     0, // cache_size
                     0, // private_data_size
                     nullptr, // mp_init
                     nullptr, // mp_init_arg
                     nullptr, // obj_init
                     nullptr, // obj_init_arg
                     0 );

Producer and consumer are running on separate threads, but that should
not be the issue since the creation flag is 0 (Multi producer/Multi
consumer). So in my scenario is chunk_count is say 128, then after 128
GET operations I get null even if I PUT back 128 items before this last
GET (and again, rte_mempool_avail_count is 128...)

Is weird, since this is happening since I've upgraded to 21.02 from
20.02.1, may I have messed up the compilation of the new DPDK? How can I
investigate this issue?


BR, Filip
+48 666 369 823

             reply	other threads:[~2021-06-30 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 13:50 Filip Janiszewski [this message]
2021-06-30 14:48 ` Muhammad Zain-ul-Abideen
2021-06-30 17:04   ` Filip Janiszewski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26c96412-1f06-2ad5-6d0e-00a8125dc81e@filipjaniszewski.com \
    --to=contact@filipjaniszewski.com \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git