All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Cc: <olivier.matz@6wind.com>, <dev@dpdk.org>, <hemant.agrawal@nxp.com>
Subject: Re: [PATCH 2/2] test/mempool_perf: support default mempool autotest
Date: Wed, 5 Apr 2017 15:32:32 +0530	[thread overview]
Message-ID: <be56e6f8-7f0a-70ee-89cb-eeaeb3e656eb@nxp.com> (raw)
In-Reply-To: <1491382264-23489-2-git-send-email-santosh.shukla@caviumnetworks.com>

Hi Santosh,

On Wednesday 05 April 2017 02:21 PM, Santosh Shukla wrote:
> Mempool_perf autotest currently does perf regression for:
>  * nochache
>  * cache
>
> Introducing default_pool, mainly targeted for ext-mempool regression
> test. Ext-mempool don't need 'cache' modes so only adding test-case
> support for 'nocache' mode.
>
> So to run ext-mempool perf regression, user has to set
> RTE_MBUF_DEFAULT_MEMPOOL_OPS="<>"
>
> There is chance of duplication  ie.. if user sets
>
> RTE_MBUF_DEFAULT_MEMPOOL_OPS="ring_mp_mc" then regression
> will happen twice for 'ring_mp_mc'
>
> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
> ---
>  test/test/test_mempool_perf.c |   41 +++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 41 insertions(+)
>
> diff --git a/test/test/test_mempool_perf.c b/test/test/test_mempool_perf.c
> index 3c45971..9c80860 100644
> --- a/test/test/test_mempool_perf.c
> +++ b/test/test/test_mempool_perf.c
> @@ -111,6 +111,7 @@
>
>  static struct rte_mempool *mp;
>  static struct rte_mempool *mp_cache, *mp_nocache;
> +static struct rte_mempool *default_pool;
>  static int use_external_cache;
>  static unsigned external_cache_size = RTE_MEMPOOL_CACHE_MAX_SIZE;
>
> @@ -337,6 +338,31 @@ struct mempool_test_stats {

Similar observations as [PATCH 1/2], the context above is not correct.
it should be test_mempool_perf(void)

>  	if (mp_cache == NULL)
>  		goto err;
>
> +	/* Create a mempool based on Default handler */
> +	default_pool = rte_mempool_create_empty("default_pool",
> +						MEMPOOL_SIZE,
> +						MEMPOOL_ELT_SIZE,
> +						0, 0,
> +						SOCKET_ID_ANY, 0);
> +
> +	if (default_pool == NULL) {
> +		printf("cannot allocate %s mempool\n",
> +			RTE_MBUF_DEFAULT_MEMPOOL_OPS);
> +		goto err;
> +	}
> +	if (rte_mempool_set_ops_byname(default_pool,
> +				RTE_MBUF_DEFAULT_MEMPOOL_OPS, NULL) < 0) {
> +		printf("cannot set %s handler\n",
> +			RTE_MBUF_DEFAULT_MEMPOOL_OPS);
> +		goto err;
> +	}
> +	if (rte_mempool_populate_default(default_pool) < 0) {
> +		printf("cannot populate %s mempool\n",
> +			RTE_MBUF_DEFAULT_MEMPOOL_OPS);
> +		goto err;
> +	}
> +	rte_mempool_obj_iter(default_pool, my_obj_init, NULL);
> +
>  	/* performance test with 1, 2 and max cores */
>  	printf("start performance test (without cache)\n");
>  	mp = mp_nocache;
> @@ -351,6 +377,20 @@ struct mempool_test_stats {
>  		goto err;
>
>  	/* performance test with 1, 2 and max cores */
> +	printf("start performance test for %s (without cache)\n",
> +			RTE_MBUF_DEFAULT_MEMPOOL_OPS);
> +	mp = default_pool;
> +
> +	if (do_one_mempool_test(1) < 0)
> +		goto err;
> +
> +	if (do_one_mempool_test(2) < 0)
> +		goto err;
> +
> +	if (do_one_mempool_test(rte_lcore_count()) < 0)
> +		goto err;
> +
> +	/* performance test with 1, 2 and max cores */
>  	printf("start performance test (with cache)\n");
>  	mp = mp_cache;
>
> @@ -384,6 +424,7 @@ struct mempool_test_stats {
>  err:
>  	rte_mempool_free(mp_cache);
>  	rte_mempool_free(mp_nocache);
> +	rte_mempool_free(default_pool);
>  	return ret;
>  }
>
>

Other than the above trivial comment:

Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>

  reply	other threads:[~2017-04-05  9:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  8:51 [PATCH 1/2] test/mempool_perf: Free mempool on exit Santosh Shukla
2017-04-05  8:51 ` [PATCH 2/2] test/mempool_perf: support default mempool autotest Santosh Shukla
2017-04-05 10:02   ` Shreyansh Jain [this message]
2017-04-05 12:40     ` santosh
2017-04-05  9:57 ` [PATCH 1/2] test/mempool_perf: Free mempool on exit Shreyansh Jain
2017-04-05 12:33   ` santosh
2017-04-06  6:45 ` [PATCH v2 " Santosh Shukla
2017-04-06  6:45   ` [PATCH v2 2/2] test/mempool_perf: support default mempool autotest Santosh Shukla
2017-04-07 15:51   ` [PATCH v2 1/2] test/mempool_perf: Free mempool on exit Olivier Matz
     [not found]     ` <BLUPR0701MB17140B8FD2D59B1A7835769FEA0E0@BLUPR0701MB1714.namprd07.prod.outlook.com>
2017-04-09 19:43       ` santosh
2017-04-10 20:09         ` Olivier MATZ
2017-04-18  8:34   ` [PATCH v3 1/3] test/test/mempool_perf: Remove mempool global vars Santosh Shukla
2017-04-18  8:34     ` [PATCH v3 2/3] test/test/mempool_perf: Free mempool on exit Santosh Shukla
2017-04-18  8:34     ` [PATCH v3 3/3] test/test/mempool_perf: support default mempool autotest Santosh Shukla
2017-04-18 13:42     ` [PATCH v3 1/3] test/test/mempool_perf: Remove mempool global vars Olivier MATZ
2017-04-18 14:39       ` santosh
2017-04-18 14:41     ` [PATCH v4 " Santosh Shukla
2017-04-18 14:41       ` [PATCH v4 2/3] test/test/mempool_perf: Free mempool on exit Santosh Shukla
2017-04-18 14:41       ` [PATCH v4 3/3] test/test/mempool_perf: support default mempool autotest Santosh Shukla
2017-04-18 15:31       ` [PATCH v4 1/3] test/test/mempool_perf: Remove mempool global vars Olivier MATZ
2017-04-19 12:48         ` [dpdk-stable] " 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=be56e6f8-7f0a-70ee-89cb-eeaeb3e656eb@nxp.com \
    --to=shreyansh.jain@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=olivier.matz@6wind.com \
    --cc=santosh.shukla@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.