From: Olivier MATZ <olivier.matz@6wind.com>
To: Zoltan Kiss <zoltan.kiss@linaro.org>, dev@dpdk.org
Subject: Re: [PATCH v2] mempool: limit cache_size
Date: Wed, 20 May 2015 10:32:03 +0200 [thread overview]
Message-ID: <555C4683.7000702@6wind.com> (raw)
In-Reply-To: <1431963314-3701-1-git-send-email-zoltan.kiss@linaro.org>
On 05/18/2015 05:35 PM, Zoltan Kiss wrote:
> Otherwise cache_flushthresh can be bigger than n, and
> a consumer can starve others by keeping every element
> either in use or in the cache.
>
> Signed-off-by: Zoltan Kiss <zoltan.kiss@linaro.org>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
> ---
> v2: use macro for calculation, with proper casting
>
> lib/librte_mempool/rte_mempool.c | 8 +++++---
> lib/librte_mempool/rte_mempool.h | 2 +-
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/lib/librte_mempool/rte_mempool.c b/lib/librte_mempool/rte_mempool.c
> index cf7ed76..5cfb96b 100644
> --- a/lib/librte_mempool/rte_mempool.c
> +++ b/lib/librte_mempool/rte_mempool.c
> @@ -68,6 +68,8 @@ static struct rte_tailq_elem rte_mempool_tailq = {
> EAL_REGISTER_TAILQ(rte_mempool_tailq)
>
> #define CACHE_FLUSHTHRESH_MULTIPLIER 1.5
> +#define CALC_CACHE_FLUSHTHRESH(c) \
> + ((typeof (c))((c) * CACHE_FLUSHTHRESH_MULTIPLIER))
>
> /*
> * return the greatest common divisor between a and b (fast algorithm)
> @@ -440,7 +442,8 @@ rte_mempool_xmem_create(const char *name, unsigned n, unsigned elt_size,
> mempool_list = RTE_TAILQ_CAST(rte_mempool_tailq.head, rte_mempool_list);
>
> /* asked cache too big */
> - if (cache_size > RTE_MEMPOOL_CACHE_MAX_SIZE) {
> + if (cache_size > RTE_MEMPOOL_CACHE_MAX_SIZE ||
> + CALC_CACHE_FLUSHTHRESH(cache_size) > n) {
> rte_errno = EINVAL;
> return NULL;
> }
> @@ -565,8 +568,7 @@ rte_mempool_xmem_create(const char *name, unsigned n, unsigned elt_size,
> mp->header_size = objsz.header_size;
> mp->trailer_size = objsz.trailer_size;
> mp->cache_size = cache_size;
> - mp->cache_flushthresh = (uint32_t)
> - (cache_size * CACHE_FLUSHTHRESH_MULTIPLIER);
> + mp->cache_flushthresh = CALC_CACHE_FLUSHTHRESH(cache_size);
> mp->private_data_size = private_data_size;
>
> /* calculate address of the first element for continuous mempool. */
> diff --git a/lib/librte_mempool/rte_mempool.h b/lib/librte_mempool/rte_mempool.h
> index 9001312..a4a9610 100644
> --- a/lib/librte_mempool/rte_mempool.h
> +++ b/lib/librte_mempool/rte_mempool.h
> @@ -468,7 +468,7 @@ typedef void (rte_mempool_ctor_t)(struct rte_mempool *, void *);
> * If cache_size is non-zero, the rte_mempool library will try to
> * limit the accesses to the common lockless pool, by maintaining a
> * per-lcore object cache. This argument must be lower or equal to
> - * CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE. It is advised to choose
> + * CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE and n / 1.5. It is advised to choose
> * cache_size to have "n modulo cache_size == 0": if this is
> * not the case, some elements will always stay in the pool and will
> * never be used. The access to the per-lcore table is of course
>
next prev parent reply other threads:[~2015-05-20 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 15:35 [PATCH v2] mempool: limit cache_size Zoltan Kiss
2015-05-18 15:51 ` Ananyev, Konstantin
2015-05-20 8:32 ` Olivier MATZ [this message]
2015-05-20 8:46 ` 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=555C4683.7000702@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=zoltan.kiss@linaro.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 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.