DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
	"Wathsala Vithanage" <wathsala.vithanage@arm.com>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH] eal: increase memzone name size to 64
Date: Tue, 13 Oct 2026 11:01:53 +0200	[thread overview]
Message-ID: <0ZnoHtjRTOGafUSZQedaXA@monjalon.net> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65A5C@smartserver.smartshare.dk>

22/09/2026 12:42, Morten Brørup:
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > --- a/lib/mempool/rte_mempool.h
> > +++ b/lib/mempool/rte_mempool.h
> > @@ -230,13 +230,11 @@ struct __rte_cache_aligned rte_mempool_info {
> >   * The RTE mempool structure.
> >   */
> >  struct __rte_cache_aligned rte_mempool {
> > -	char name[RTE_MEMPOOL_NAMESIZE]; /**< Name of mempool. */
> >  	union {
> >  		void *pool_data;         /**< Ring or pool to store
> > objects. */
> >  		uint64_t pool_id;        /**< External mempool identifier.
> > */
> >  	};
> > -	void *pool_config;               /**< optional args for ops
> > alloc. */
> > -	const struct rte_memzone *mz;    /**< Memzone where pool is
> > alloc'd. */
> > +	struct rte_mempool_cache *local_cache; /**< Per-lcore local cache
> > */
> >  	unsigned int flags;              /**< Flags of the mempool. */
> >  	int socket_id;                   /**< Socket id passed at create.
> > */
> >  	uint32_t size;                   /**< Max size of the mempool. */
> > @@ -257,7 +255,9 @@ struct __rte_cache_aligned rte_mempool {
> >  	 */
> >  	int32_t ops_index;
> > 
> > -	struct rte_mempool_cache *local_cache; /**< Per-lcore local cache
> > */
> > +	void *pool_config;               /**< optional args for ops
> > alloc. */
> > +	const struct rte_memzone *mz;    /**< Memzone where pool is
> > alloc'd. */
> > +	char name[RTE_MEMPOOL_NAMESIZE]; /**< Name of mempool. */
> > 
> >  	uint32_t populated_size;         /**< Number of populated
> > objects. */
> >  	struct rte_mempool_objhdr_list elt_list; /**< List of objects in
> > pool */
> 
> I have submitted a patch introducing a new "sizeof_cache_per_lcore" field [1].
> This new field must be close to the "local_cache" field.
> 
> Also, for mempool cache misses, the "ops_index" and "pool_data" fields should be close together. Optimally also close to the "local_cache" field, so they have been fetched with it.
> 
> [1]: https://patchwork.dpdk.org/project/dpdk/patch/20260910103613.808038-7-mb@smartsharesystems.com/
> 
> AFAIK, only these four fields hot in the dataplane:
> - local_cache, sizeof_cache_per_lcore (new field):
>   Used for access to objects in cache.
> - ops_index, pool_data/pool_id:
>   Used on cache miss for access to objects in backing store.
> 
> The other fields are not used in the dataplane, and can be moved down below these four, which should be first.
> 
> Note: The cache_size field is currently hot, but my patch makes it cold.

These changes in mempool are marged in main.
So this memzone series needs to be rebased.



  reply	other threads:[~2026-10-13  9:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 21:57 [PATCH] eal: increase memzone name size to 64 Stephen Hemminger
2026-09-22 10:42 ` Morten Brørup
2026-10-13  9:01   ` Thomas Monjalon [this message]
2026-09-22 15:52 ` [PATCH v2 0/3] increase memzone name size and fix rib/fib prefixes Stephen Hemminger
2026-09-22 15:52   ` [PATCH v2 1/3] app/crypto-perf: fix asymmetric op pool name size Stephen Hemminger
2026-09-22 18:25     ` [EXTERNAL] " Akhil Goyal
2026-09-22 15:52   ` [PATCH v2 2/3] eal: increase memzone name size to 64 Stephen Hemminger
2026-10-13  9:02     ` Thomas Monjalon
2026-09-22 15:52   ` [PATCH v2 3/3] fib, rib: fix name prefixes Stephen Hemminger
2026-09-22 19:46     ` Medvedkin, Vladimir

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=0ZnoHtjRTOGafUSZQedaXA@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.org \
    --cc=wathsala.vithanage@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox