All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Pang <robertpang@google.com>
To: Coly Li <colyli@kernel.org>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	 linux-bcache@vger.kernel.org
Cc: Robert Pang <robertpang@google.com>,
	Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [PATCH 0/3] bcache: Fix the tail IO latency regression due to the use of lib min_heap
Date: Fri,  6 Jun 2025 00:19:42 -0700	[thread overview]
Message-ID: <20250606071959.1685079-1-robertpang@google.com> (raw)

This patch series reverts bcache to its original top-down heap sifting strategy
for LRG cache replacement, which fixes a tail I/O latency regression.

Discussion: https://lore.kernel.org/linux-bcache/wtfuhfntbi6yorxqtpcs4vg5w67mvyckp2a6jmxuzt2hvbw65t@gznwsae5653d/T/#me50a9ddd0386ce602b2f17415e02d33b8e29f533

Robert Pang (3):
  lib min_heap: refactor min_heap to allow the alternative sift-down
    function to be used
  lib min_heap: add alternative APIs that use the conventional top-down
    strategy to sift down elements
  bcache: Fix the tail IO latency regression due to the use of lib
    min_heap

 drivers/md/bcache/alloc.c |  14 ++--
 include/linux/min_heap.h  | 135 ++++++++++++++++++++++++++++++++------
 lib/min_heap.c            |  31 ++++++---
 3 files changed, 145 insertions(+), 35 deletions(-)

-- 
2.50.0.rc1.591.g9c95f17f64-goog


             reply	other threads:[~2025-06-06  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  7:19 Robert Pang [this message]
2025-06-06  7:19 ` [PATCH 1/3] lib min_heap: refactor min_heap to allow the alternative sift-down function to be used Robert Pang
2025-06-06  7:19 ` [PATCH 2/3] lib min_heap: add alternative APIs that use the conventional top-down strategy to sift down elements Robert Pang
2025-06-06 12:52   ` Kuan-Wei Chiu
2025-06-06  7:19 ` [PATCH 3/3] bcache: Fix the tail IO latency regression due to the use of lib min_heap Robert Pang
2025-06-06 13:01   ` Kuan-Wei Chiu
2025-06-10 12:44     ` Robert Pang

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=20250606071959.1685079-1-robertpang@google.com \
    --to=robertpang@google.com \
    --cc=colyli@kernel.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcache@vger.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 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.