From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: akpm@linux-foundation.org
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, namhyung@kernel.org, irogers@google.com,
adrian.hunter@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [RESEND PATCH v2 0/2] lib min_heap: Min heap optimizations
Date: Wed, 10 Jan 2024 16:12:11 +0800 [thread overview]
Message-ID: <20240110081213.2289636-1-visitorckw@gmail.com> (raw)
Hello,
The purpose of this patch series is to enhance the existing min heap
implementation. The optimization focuses on both the heap construction
process and the number of comparisons made during the heapify
operation.
Thanks,
Kuan-Wei Chiu
---
Changes in RESEND:
- CC the mailing list
Changes in RESEND:
- CC performance events subsystem's maintainers and reviewers.
Link: https://lkml.kernel.org/20240103205259.2108410-1-visitorckw@gmail.com
Changes in v2:
- Use a more consistent title: "min_heap:" -> "lib min_heap:"
- Refine commit messages
Link: https://lkml.kernel.org/20231220083224.3712113-1-visitorckw@gmail.com
Kuan-Wei Chiu (2):
lib min_heap: Optimize number of calls to min_heapify()
lib min_heap: Optimize number of comparisons in min_heapify()
include/linux/min_heap.h | 44 +++++++++++++++++++++-------------------
1 file changed, 23 insertions(+), 21 deletions(-)
--
2.25.1
next reply other threads:[~2024-01-10 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 8:12 Kuan-Wei Chiu [this message]
2024-01-10 8:12 ` [RESEND PATCH v2 1/2] lib min_heap: Optimize number of calls to min_heapify() Kuan-Wei Chiu
2024-01-10 8:12 ` [RESEND PATCH v2 2/2] lib min_heap: Optimize number of comparisons in min_heapify() 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=20240110081213.2289636-1-visitorckw@gmail.com \
--to=visitorckw@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 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).