From: "Morten Brørup" <mb@smartsharesystems.com>
To: <andrew.rybchenko@oktetlabs.ru>, <fengchengwen@huawei.com>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH v2] mempool: test performance with larger bursts
Date: Mon, 22 Jan 2024 15:39:15 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F184@smartserver.smartshare.dk> (raw)
In-Reply-To: <20240122142708.45026-1-mb@smartsharesystems.com>
Replied on wrong thread. Sorry.
Resubmitted with correct in-reply-to.
-Morten
next prev parent reply other threads:[~2024-01-22 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 5:32 [RFC] mbuf: performance optimization Morten Brørup
2024-01-21 17:07 ` Stephen Hemminger
2024-01-21 17:19 ` Morten Brørup
2024-01-22 14:27 ` [PATCH v2] mempool: test performance with larger bursts Morten Brørup
2024-01-22 14:39 ` Morten Brørup [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-21 4:52 [PATCH] " Morten Brørup
2024-01-22 14:34 ` [PATCH v2] " Morten Brørup
2024-01-24 2:41 ` fengchengwen
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=98CBD80474FA8B44BF855DF32C47DC35E9F184@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.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;
as well as URLs for NNTP newsgroup(s).