From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Jingjing Wu <jingjing.wu@intel.com>,
Praveen Shetty <praveen.shetty@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH v7] net/idpf: update for new mempool cache algorithm
Date: Wed, 10 Jun 2026 12:31:26 +0100 [thread overview]
Message-ID: <ailLDte3Xo8jsUWf@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65902@smartserver.smartshare.dk>
On Wed, Jun 10, 2026 at 01:21:38PM +0200, Morten Brørup wrote:
> Intel idpf maintainers,
>
> PING for review.
>
> The mempool library has been improved [1], so the idpf PMD - which bypasses the mempool API - must be updated to match the library implementation. This patch does that.
>
> [1]: https://git.dpdk.org/dpdk/commit/?id=f5e1310f16e0909e7e7f71807123644c63b23cba
>
>
> Venlig hilsen / Kind regards,
> -Morten Brørup
>
Yep. I was waiting to see what happened to the mempool patch before
considering this for next-net-intel.
/Bruce
next prev parent reply other threads:[~2026-06-10 11:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 14:13 [PATCH] mempool: improve cache behaviour and performance Morten Brørup
2026-04-08 15:41 ` Stephen Hemminger
2026-04-09 10:25 ` [PATCH v2] " Morten Brørup
2026-04-09 11:05 ` [PATCH v3] " Morten Brørup
2026-04-15 13:40 ` Morten Brørup
2026-04-18 11:15 ` [PATCH v4] " Morten Brørup
2026-04-19 9:55 ` [PATCH v5] " Morten Brørup
2026-04-22 12:27 ` Morten Brørup
2026-04-27 15:21 ` Morten Brørup
2026-04-28 7:44 ` Andrew Rybchenko
2026-05-22 16:11 ` Bruce Richardson
2026-05-26 8:41 ` Morten Brørup
2026-05-26 9:39 ` Bruce Richardson
2026-05-26 10:37 ` Morten Brørup
2026-05-26 17:45 ` Morten Brørup
2026-05-27 8:48 ` Bruce Richardson
2026-05-27 9:22 ` Morten Brørup
2026-05-22 16:12 ` Bruce Richardson
2026-05-26 8:57 ` Morten Brørup
2026-05-26 14:00 ` [PATCH v6] " Morten Brørup
2026-05-26 16:00 ` Morten Brørup
2026-06-01 13:36 ` Thomas Monjalon
2026-06-01 13:51 ` Morten Brørup
2026-06-01 14:19 ` Thomas Monjalon
2026-06-01 14:27 ` Morten Brørup
2026-05-29 8:53 ` fengchengwen
2026-05-29 11:43 ` Morten Brørup
2026-05-27 11:36 ` [PATCH v6] net/idpf: update for new mempool cache algorithm Morten Brørup
2026-05-27 11:36 ` [PATCH v6] mempool/dpaa: " Morten Brørup
2026-05-27 11:36 ` [PATCH v6] mempool/dpaa2: " Morten Brørup
2026-06-01 16:40 ` [PATCH v7] mempool: improve cache behaviour and performance Morten Brørup
2026-06-03 15:44 ` Thomas Monjalon
2026-06-01 18:36 ` [PATCH v7] net/idpf: update for new mempool cache algorithm Morten Brørup
2026-06-01 18:36 ` [PATCH v7] mempool/dpaa: " Morten Brørup
2026-06-02 6:51 ` Morten Brørup
2026-06-01 18:36 ` [PATCH v7] mempool/dpaa2: " Morten Brørup
2026-06-02 6:53 ` Morten Brørup
2026-06-02 6:45 ` [PATCH v7] net/idpf: " Morten Brørup
2026-06-10 11:21 ` Morten Brørup
2026-06-10 11:31 ` Bruce Richardson [this message]
2026-06-10 12:17 ` Thomas Monjalon
2026-06-10 12:34 ` Bruce Richardson
2026-06-10 11:31 ` Morten Brørup
2026-06-04 11:48 ` [PATCH v8] mempool: improve cache behaviour and performance Morten Brørup
2026-06-04 13:57 ` Morten Brørup
2026-06-10 11:06 ` Thomas Monjalon
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=ailLDte3Xo8jsUWf@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=mb@smartsharesystems.com \
--cc=praveen.shetty@intel.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