All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [RFC PATCH v2] mempool: optimizations
Date: Thu, 13 Aug 2026 16:30:24 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F659E1@smartserver.smartshare.dk> (raw)
In-Reply-To: an2w6xvcssfVEjTB@bricha3-mobl1.ger.corp.intel.com

> From: Morten Brørup
> Sent: Thursday, 13 August 2026 14.57
> 
> > > +* mempool: The obsolete ``flushthresh`` field was removed from the
> > > ``rte_mempool_cache`` structure.  + * Removed deprecated symbols:
> > >
> > I'm not convinced about removing this field at this point. Based on
> > previous discussions around run-to-completion vs pipeline apps, and
> the
> > reported performance degradations due to recent cache changes, I
> could
> > see a scenario where it's useful to track a separate flushthreshold
> or
> > cache-keep threshold for a mempool.
> 
> Removing the flushthresh field is part of the cleanup patch [1].
> I merged that patch into this one because I'm having problems with
> Depends-on.

The separate patch with the new optimizations only [2] that was merged into this patch (due to Depends-on problems) was marked as Superseded in Patchwork. I changed it back to New, so it is present for stand-alone review.

[1]: https://patchwork.dpdk.org/project/dpdk/patch/20260806154506.1532375-1-mb@smartsharesystems.com/
[2]: https://patchwork.dpdk.org/project/dpdk/patch/20260812090723.1771628-1-mb@smartsharesystems.com/


  parent reply	other threads:[~2026-08-13 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12  9:07 [PATCH] mempool: optimizations Morten Brørup
2026-08-12 12:06 ` [RFC PATCH v2] " Morten Brørup
2026-08-13 11:56   ` Bruce Richardson
2026-08-13 12:56     ` Morten Brørup
2026-08-13 14:30     ` Morten Brørup [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-12  9:58 Morten Brørup
2026-08-12 12:08 ` 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=98CBD80474FA8B44BF855DF32C47DC35F659E1@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@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.