From: Ali Alnubani <alialnu@nvidia.com>
To: "Thomas Monjalon" <thomas@monjalon.net>,
"Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v7 0/2] introduce pile stack and mempool driver
Date: Mon, 19 Oct 2026 16:56:23 +0300 [thread overview]
Message-ID: <f515d29c-525d-4854-bede-ffcc01303062@nvidia.com> (raw)
In-Reply-To: <ItqMX3UyR721OV9AeSB9fA@monjalon.net>
On 10/15/26 8:22 PM, Thomas Monjalon wrote:
> 14/09/2026 17:58, Morten Brørup:
>> Added a new high-performance lock-free "pile", using the Stack API,
>> and an accompanying mempool driver.
>>
>> Morten Brørup (2):
>> stack: introduce pile
>> mempool: introduce pile driver
> Applied, thanks.
Hello,
Debug build fails on Ubuntu 24.04 (aarch64) with this patchset. Bug:
https://bugs.dpdk.org/show_bug.cgi?id=2061
Regards,
Ali
next prev parent reply other threads:[~2026-10-19 13:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 13:47 [PATCH] stack: introduce pile Morten Brørup
2026-08-12 14:34 ` Bruce Richardson
2026-08-12 16:01 ` Morten Brørup
2026-08-12 16:15 ` Bruce Richardson
2026-08-12 16:28 ` Morten Brørup
2026-08-13 11:50 ` Bruce Richardson
2026-08-17 13:10 ` Bruce Richardson
2026-08-18 8:11 ` Konstantin Ananyev
2026-08-18 8:50 ` Morten Brørup
2026-08-25 7:05 ` Konstantin Ananyev
2026-08-25 9:21 ` Morten Brørup
2026-08-25 11:29 ` Konstantin Ananyev
2026-08-26 8:13 ` Konstantin Ananyev
2026-08-27 13:55 ` [PATCH v3 0/2] introduce pile stack and mempool driver Morten Brørup
2026-08-27 13:55 ` [PATCH v3 1/2] stack: introduce pile Morten Brørup
2026-08-31 8:50 ` Konstantin Ananyev
2026-08-31 9:05 ` Morten Brørup
2026-08-31 9:38 ` Konstantin Ananyev
2026-08-31 10:09 ` Morten Brørup
2026-08-31 16:06 ` Stephen Hemminger
2026-08-31 16:37 ` Morten Brørup
2026-08-27 13:55 ` [PATCH v3 2/2] mempool: introduce pile driver Morten Brørup
2026-09-01 6:43 ` [PATCH v4 0/2] introduce pile stack and mempool driver Morten Brørup
2026-09-01 6:43 ` [PATCH v4 1/2] stack: introduce pile Morten Brørup
2026-09-01 6:43 ` [PATCH v4 2/2] mempool: introduce pile driver Morten Brørup
2026-09-02 16:00 ` Stephen Hemminger
2026-09-14 10:45 ` [PATCH v5 0/2] introduce pile stack and mempool driver Morten Brørup
2026-09-14 10:45 ` [PATCH v5 1/2] stack: introduce pile Morten Brørup
2026-09-14 10:45 ` [PATCH v5 2/2] mempool: introduce pile driver Morten Brørup
2026-09-14 14:44 ` [PATCH v6 0/2] introduce pile stack and mempool driver Morten Brørup
2026-09-14 14:44 ` [PATCH v6 1/2] stack: introduce pile Morten Brørup
2026-09-14 14:44 ` [PATCH v6 2/2] mempool: introduce pile driver Morten Brørup
2026-09-14 15:58 ` [PATCH v7 0/2] introduce pile stack and mempool driver Morten Brørup
2026-09-14 15:59 ` [PATCH v7 1/2] stack: introduce pile Morten Brørup
2026-09-14 15:59 ` [PATCH v7 2/2] mempool: introduce pile driver Morten Brørup
2026-10-15 17:22 ` [PATCH v7 0/2] introduce pile stack and mempool driver Thomas Monjalon
2026-10-19 13:56 ` Ali Alnubani [this message]
2026-10-19 16:39 ` 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=f515d29c-525d-4854-bede-ffcc01303062@nvidia.com \
--to=alialnu@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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