Linux-EROFS Archive on 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: Mon, 15 Jun 2026 08:15:12 +0530	[thread overview]
Message-ID: <20260615024512.94930-1-nithurshen.dev@gmail.com> (raw)
In-Reply-To: <555d6eec-7ddf-451e-98a3-70f7612a98c6@linux.alibaba.com>

Hi Xiang,

Understood. I will drop the userspace metadata caching patches for now, 
as it is not the current priority.

I will shift my focus entirely to the concurrent directory traversal 
patch (Phase 3) that I submitted recently. Please let me know your 
thoughts on this.

Thanks,
Nithurshen


  reply	other threads:[~2026-06-15  2:45 UTC|newest]

Thread overview: 6+ 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
2026-06-15  1:48     ` Gao Xiang
2026-06-15  2:45       ` 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=20260615024512.94930-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox