From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>, "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [RFC PATCH v2] mempool: optimizations
Date: Wed, 12 Aug 2026 14:08:50 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F659D9@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260812095836.1771949-1-mb@smartsharesystems.com>
PLEASE IGNORE.
--in-reply-to was missing.
I have sent another mail with --in-reply-to.
Venlig hilsen / Kind regards,
-Morten Brørup
> -----Original Message-----
> From: Morten Brørup [mailto:mb@smartsharesystems.com]
> Sent: Wednesday, 12 August 2026 11.59
> To: dev@dpdk.org; Andrew Rybchenko
> Cc: Morten Brørup
> Subject: [RFC PATCH v2] mempool: optimizations
next prev parent reply other threads:[~2026-08-12 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 9:58 [RFC PATCH v2] mempool: optimizations Morten Brørup
2026-08-12 12:08 ` Morten Brørup [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-12 9:07 [PATCH] " 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
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=98CBD80474FA8B44BF855DF32C47DC35F659D9@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox