From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] erofs: support read directory inodes with metabuf
Date: Wed, 16 Mar 2022 10:52:36 +0800 [thread overview]
Message-ID: <e3611a21-cbed-74c4-e596-e0e628de9b70@kernel.org> (raw)
In-Reply-To: <20220316012246.95131-1-hsiangkao@linux.alibaba.com>
On 2022/3/16 9:22, Gao Xiang wrote:
> Previously, directory inodes are directly handled with page cache
> interfaces.
>
> In order to support sub-page directory blocks and folios, let's
> convert them into the latest metabuf infrastructure as well and
> this patch addresses the readdir case first.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2022-03-16 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 1:22 [PATCH 1/2] erofs: support read directory inodes with metabuf Gao Xiang
2022-03-16 1:22 ` [PATCH 2/2] erofs: support inode lookup " Gao Xiang
2022-03-16 3:29 ` Chao Yu
2022-03-16 2:52 ` Chao Yu [this message]
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=e3611a21-cbed-74c4-e596-e0e628de9b70@kernel.org \
--to=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.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