mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xavier  <xavier_qy@163.com>
To: "Kuan-Wei Chiu" <visitorckw@gmail.com>
Cc: longman@redhat.com, lizefan.x@bytedance.com, tj@kernel.org,
	 hannes@cmpxchg.org, mkoutny@suse.com, akpm@linux-foundation.org,
	 jserv@ccns.ncku.edu.tw, linux-kernel@vger.kernel.org,
	 cgroups@vger.kernel.org
Subject: Re:[PATCH 4/5] lib/union_find: Optimize uf_find() with enhanced path compression
Date: Mon, 7 Oct 2024 21:18:52 +0800 (CST)	[thread overview]
Message-ID: <18b085ce.3da3.1926721f823.Coremail.xavier_qy@163.com> (raw)
In-Reply-To: <20241005214938.2147393-5-visitorckw@gmail.com>



At 2024-10-06 05:49:37, "Kuan-Wei Chiu" <visitorckw@gmail.com> wrote:
>Optimize the uf_find() function to enhance its efficiency by
>implementing a more effective path compression strategy. The original
>implementation only updated the parent pointer of the current node to
>its grandparent, resulting in a relatively shallow tree.
>
>In the updated version, once the root of the node is identified, all
>nodes along the search path are updated to directly point to the root.
>This change minimizes the height of the tree and improves the
>efficiency for subsequent find operations, providing better performance
>for the Union-Find data structure.
>
>Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
>---
>Note: Tested with the KUnit tests introduced in the previous patch.
>
> lib/union_find.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
>diff --git a/lib/union_find.c b/lib/union_find.c
>index a20678da0220..7c553fa622c8 100644
>--- a/lib/union_find.c
>+++ b/lib/union_find.c
>@@ -13,14 +13,19 @@
>  */
> struct uf_node *uf_find(struct uf_node *node)
> {
>+	struct uf_node *root = node;
> 	struct uf_node *parent;
> 
>+	while (root->parent != root)
>+		root = root->parent;
>+
> 	while (node->parent != node) {

Using “root” for this judgment might be better, as it could
reduce unnecessary entering.
        while (node->parent != root) {

> 		parent = node->parent;
>-		node->parent = parent->parent;
>+		node->parent = root;
> 		node = parent;
> 	}
>-	return node;
>+
>+	return root;
> }
> EXPORT_SYMBOL(uf_find);
> 
>-- 
>2.34.1

  reply	other threads:[~2024-10-07 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 21:49 [PATCH 0/5] Enhance Union-Find with KUnit tests and optimization improvements Kuan-Wei Chiu
2024-10-05 21:49 ` [PATCH 1/5] lib/union_find: Add EXPORT_SYMBOL() for uf_find() and uf_union() Kuan-Wei Chiu
2024-10-05 21:49 ` [PATCH 2/5] lib/union_find: Change uf_union() return type to bool Kuan-Wei Chiu
2024-10-05 21:49 ` [PATCH 3/5] lib: Add KUnit tests for Union-Find implementation Kuan-Wei Chiu
2024-10-07 13:14   ` Xavier
2024-10-05 21:49 ` [PATCH 4/5] lib/union_find: Optimize uf_find() with enhanced path compression Kuan-Wei Chiu
2024-10-07 13:18   ` Xavier [this message]
2024-10-05 21:49 ` [PATCH 5/5] cgroup/cpuset: Optimize total domain count using updated uf_union() Kuan-Wei Chiu

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=18b085ce.3da3.1926721f823.Coremail.xavier_qy@163.com \
    --to=xavier_qy@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=tj@kernel.org \
    --cc=visitorckw@gmail.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

all inboxes | Powered by JetHome®