DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ashwin Sekhar T K <asekhar@marvell.com>
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
	 Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	 Satha Rao <skoteshwar@marvell.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	jerinj@marvell.com,  psatheesh@marvell.com, anoobj@marvell.com,
	gakhil@marvell.com,  hkalra@marvell.com
Subject: Re: [PATCH 1/3] mempool/cnxk: limit usage of async allocs
Date: Thu, 24 Aug 2023 10:27:24 +0530	[thread overview]
Message-ID: <CALBAE1MBdgqKPwGueSHsARp73Lf58tu58oe6CNEP0Z6WxLcG0w@mail.gmail.com> (raw)
In-Reply-To: <20230822170157.2637286-1-asekhar@marvell.com>

On Tue, Aug 22, 2023 at 10:40 PM Ashwin Sekhar T K <asekhar@marvell.com> wrote:
>
> Currently mempool_cnxk driver uses asynchronous allocation
> for all pools. This asynchronous allocation can result in
> local caching of additional 512 objects on a single core
> even when cache is disabled. This will eventually lead to
> starvation on pools where the number of objects is very less.
>
> This commit changes this logic to use asynchronous allocation on
> only those pools which have local cache enabled. Also the async buffer
> size will be RTE_ALIGN_CEIL(rte_mempool->cache_size, 16). This
> means that when cache is disabled, async alloc will be completely
> disabled and when cache is enabled, the additional caching due
> to asynchronous allocation will be limited.
>
> A limitation has been added to cnxk documentation warning the users
> to adjust the local cache sizes accordingly.
>
> Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>

Series applied to dpdk-next-net-mrvl/for-next-net. Thanks

      parent reply	other threads:[~2023-08-24  4:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  5:55 [PATCH 1/2] " Ashwin Sekhar T K
2023-07-31  5:55 ` [PATCH 2/2] mempool/cnxk: fix alloc from non-EAL pthreads Ashwin Sekhar T K
2023-08-18  9:21   ` Jerin Jacob
2023-08-22 17:01 ` [PATCH 1/3] mempool/cnxk: limit usage of async allocs Ashwin Sekhar T K
2023-08-22 17:01   ` [PATCH 2/3] mempool/cnxk: fix free from non-EAL pthreads Ashwin Sekhar T K
2023-08-22 17:01   ` [PATCH 3/3] mempool/cnxk: fix alloc " Ashwin Sekhar T K
2023-08-24  4:57   ` Jerin Jacob [this message]

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=CALBAE1MBdgqKPwGueSHsARp73Lf58tu58oe6CNEP0Z6WxLcG0w@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=anoobj@marvell.com \
    --cc=asekhar@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.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).