DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Morten Brørup" <mb@smartsharesystems.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	dev@dpdk.org
Subject: Re: [PATCH v2 0/4] mempool perf test: test random bulk sizes
Date: Mon, 31 Mar 2025 17:48:38 +0300	[thread overview]
Message-ID: <f49fb9ed-0e34-4752-960a-f2b26bd14b89@oktetlabs.ru> (raw)
In-Reply-To: <20250331100343.213430-1-mb@smartsharesystems.com>

On 3/31/25 13:03, Morten Brørup wrote:
> Bulk requests to get or put objects in a mempool often vary in size.
> A series of tests with pseudo random request sizes, to mitigate the
> benefits of the CPU's dynamic branch predictor, was added.
> 
> Also, various other minor changes:
> - Improved the output formatting for readability.
> - Added test for the "default" mempool with cache.
> - Skip the tests for the "default" mempool, if it happens to use the same
>    driver (i.e. operations) as already tested.
> - Replaced bare use of "unsigned" with "unsigned int",
>    to make checkpatches happy.
> 
> v2:
> * Split patch into individual patches. (Andrew Rybchenko)

Thanks Morten, LGTM except a couple of nits

> 
> Morten Brørup (4):
>    mempool perf test: replace bare unsigned with unsigned int
>    mempool perf test: test default mempool with cache
>    mempool perf test: improve output readability
>    mempool perf test: test random bulk sizes
> 
>   app/test/test_mempool_perf.c | 222 +++++++++++++++++++++++++++--------
>   1 file changed, 173 insertions(+), 49 deletions(-)
> 


  parent reply	other threads:[~2025-03-31 14:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 16:48 [PATCH] " Morten Brørup
2025-03-13  8:23 ` Morten Brørup
2025-03-25  7:15   ` Morten Brørup
2025-03-30  8:29 ` Andrew Rybchenko
2025-03-30  8:57   ` Morten Brørup
2025-03-31 10:03 ` [PATCH v2 0/4] " Morten Brørup
2025-03-31 10:03   ` [PATCH v2 1/4] mempool perf test: replace bare unsigned with unsigned int Morten Brørup
2025-03-31 10:03   ` [PATCH v2 2/4] mempool perf test: test default mempool with cache Morten Brørup
2025-03-31 10:03   ` [PATCH v2 3/4] mempool perf test: improve output readability Morten Brørup
2025-03-31 10:03   ` [PATCH v2 4/4] mempool perf test: test random bulk sizes Morten Brørup
2025-03-31 14:48     ` Andrew Rybchenko
2025-04-02  9:07       ` Morten Brørup
2025-03-31 14:48   ` Andrew Rybchenko [this message]
2025-04-01 15:00 ` [PATCH v2 0/4] " Morten Brørup
2025-04-01 15:00   ` [PATCH v2 1/4] mempool perf test: replace bare unsigned with unsigned int Morten Brørup
2025-04-01 15:00   ` [PATCH v2 2/4] mempool perf test: test default mempool with cache Morten Brørup
2025-04-01 15:00   ` [PATCH v2 3/4] mempool perf test: improve output readability Morten Brørup
2025-04-01 15:00   ` [PATCH v2 4/4] mempool perf test: test random bulk sizes Morten Brørup
2025-04-01 15:02 ` [PATCH v3 0/4] " Morten Brørup
2025-04-01 15:02   ` [PATCH v3 1/4] mempool perf test: replace bare unsigned with unsigned int Morten Brørup
2025-04-01 15:02   ` [PATCH v3 2/4] mempool perf test: test default mempool with cache Morten Brørup
2025-04-01 15:02   ` [PATCH v3 3/4] mempool perf test: improve output readability Morten Brørup
2025-04-01 15:02   ` [PATCH v3 4/4] mempool perf test: test random bulk sizes 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=f49fb9ed-0e34-4752-960a-f2b26bd14b89@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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).