All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nithurshen <nithurshen.dev@gmail.com>
To: hsiangkao@linux.alibaba.com
Cc: linux-erofs@lists.ozlabs.org, nithurshen.dev@gmail.com, xiang@kernel.org
Subject: Re: [PATCH v1] fsck.erofs: implement thread-safe global LRU metadata cache
Date: Sat, 13 Jun 2026 15:40:38 +0530	[thread overview]
Message-ID: <20260613101038.86333-1-nithurshen.dev@gmail.com> (raw)
In-Reply-To: <423c662c-e8b4-4802-b7bf-34abd71a82ae@linux.alibaba.com>

Hi Xiang,

What if rather than caching the raw metadata bytes, the userspace
cache will focus on caching the parsed structures (such as the
computed erofs_map_blocks mappings) to save the worker threads
from redundantly parsing chunk indexes and calculating offsets.

Can I replace this malloc-based raw buffer approach and focus v3
patch on an LRU cache for the parsed block mappings to reduce the
CPU overhead during the concurrent directory traversal?

Thanks,
Nithurshen


  reply	other threads:[~2026-06-13 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  8:36 [PATCH v1] fsck.erofs: implement thread-safe global LRU metadata cache Nithurshen
2026-06-11  9:15 ` Gao Xiang
2026-06-13 10:10   ` Nithurshen [this message]
2026-06-11 18:46 ` [PATCH v2] " Nithurshen

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=20260613101038.86333-1-nithurshen.dev@gmail.com \
    --to=nithurshen.dev@gmail.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=xiang@kernel.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 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.