DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Abdullah Ömer Yamaç" <aomeryamac@gmail.com>
To: dev@dpdk.org
Cc: dharmik.thakkar@arm.com,
	 Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Yipeng Wang <yipeng1.wang@intel.com>,
	 Sameh Gobriel <sameh.gobriel@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	 Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] lib/hash: setting the maximum reclamation size
Date: Tue, 23 Apr 2024 16:51:58 +0300	[thread overview]
Message-ID: <CA+sj1i_Ff8rcVY5jmrpBhCsm1GO3W1J5oja1ZbYsxtRD0g_fSw@mail.gmail.com> (raw)
In-Reply-To: <20240417133929.711268-1-aomeryamac@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]

Hello,
Any comment on this patch?

On Wed, Apr 17, 2024 at 4:39 PM Abdullah Ömer Yamaç <aomeryamac@gmail.com>
wrote:

> In the previous implementation, the maximum reclamation size was set
> to RTE_HASH_RCU_DQ_RECLAIM_MAX and it was not configurable. This patch
> uses the configuration argument to set the maximum reclamation size.
>
> Fixes: 769b2de7fb52 ("hash: implement RCU resources reclamation")
> Cc: dharmik.thakkar@arm.com
> Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Cc: Yipeng Wang <yipeng1.wang@intel.com>
> Cc: Sameh Gobriel <sameh.gobriel@intel.com>
> Cc: Bruce Richardson <bruce.richardson@intel.com>
> Cc: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
>
> Signed-off-by: Abdullah Ömer Yamaç <aomeryamac@gmail.com>
> ---
>  lib/hash/rte_cuckoo_hash.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/lib/hash/rte_cuckoo_hash.c b/lib/hash/rte_cuckoo_hash.c
> index 4a44aadd9a..6d80793164 100644
> --- a/lib/hash/rte_cuckoo_hash.c
> +++ b/lib/hash/rte_cuckoo_hash.c
> @@ -1557,6 +1557,7 @@ rte_hash_rcu_qsbr_add(struct rte_hash *h, struct
> rte_hash_rcu_config *cfg)
>                 if (params.size == 0)
>                         params.size = total_entries;
>                 params.trigger_reclaim_limit = cfg->trigger_reclaim_limit;
> +               params.max_reclaim_size = cfg->max_reclaim_size;
>                 if (params.max_reclaim_size == 0)
>                         params.max_reclaim_size =
> RTE_HASH_RCU_DQ_RECLAIM_MAX;
>                 params.esize = sizeof(struct __rte_hash_rcu_dq_entry);
> --
> 2.34.1
>
>

[-- Attachment #2: Type: text/html, Size: 2511 bytes --]

  reply	other threads:[~2024-04-23 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 13:39 Abdullah Ömer Yamaç
2024-04-23 13:51 ` Abdullah Ömer Yamaç [this message]
2024-05-10  3:08   ` Abdullah Ömer Yamaç
2024-05-13  5:29 ` Honnappa Nagarahalli
2024-05-13 10:00   ` [PATCH v2] lib/hash: Set the maximum reclamation size to user provided value Abdullah Ömer Yamaç
2024-05-13 14:34     ` Honnappa Nagarahalli
2024-05-13 15:22       ` Abdullah Ömer Yamaç
2024-05-13 16:17         ` Honnappa Nagarahalli
2024-05-13 16:35           ` [PATCH v3] lib/hash: setting the maximum reclamation size Abdullah Ömer Yamaç
2024-05-14 20:52             ` Honnappa Nagarahalli

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=CA+sj1i_Ff8rcVY5jmrpBhCsm1GO3W1J5oja1ZbYsxtRD0g_fSw@mail.gmail.com \
    --to=aomeryamac@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dharmik.thakkar@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=sameh.gobriel@intel.com \
    --cc=thomas@monjalon.net \
    --cc=vladimir.medvedkin@intel.com \
    --cc=yipeng1.wang@intel.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).