All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [RFC PATCH] mempool: no cache size limit
Date: Mon, 7 Sep 2026 10:07:05 -0700	[thread overview]
Message-ID: <20260907100705.105ef931@phoenix.local> (raw)
In-Reply-To: <20260907120605.969197-1-mb@smartsharesystems.com>

On Mon,  7 Sep 2026 12:06:05 +0000
Morten Brørup <mb@smartsharesystems.com> wrote:

> Replaced the object array of fixed size in the per-lcore local cache
> with a dynamically sized array, thereby making the
> RTE_MEMPOOL_CACHE_MAX_SIZE superfluous.
> For faster indexing into the per-lcore array of caches, pre-calculate
> the size (in bytes) of the per-lcore local cache.
> 
> Also swapped the position of the private data and the local caches;
> the private data now are positioned before the local caches, instead
> of after.
> Positioning the private data directly after the mempool header reduces
> getting the private data pointer to simply adding a constant.
> The local caches are accessed by dereferencing a pointer anyway, so the
> performance for accessing these is unaffected by moving their position.
> 
> Comments, please?
> 
> We should probably keep RTE_MEMPOOL_CACHE_MAX_SIZE in rte_config.h for
> DPDK 26.11, and deprecate it as obsolete.
> 
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>

Maybe have a very large upper bound to prevent bugs from broken programs?

  reply	other threads:[~2026-09-07 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 12:06 [RFC PATCH] mempool: no cache size limit Morten Brørup
2026-09-07 17:07 ` Stephen Hemminger [this message]
2026-09-08 15:14 ` [PATCH v2] " Morten Brørup

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=20260907100705.105ef931@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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 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.