From: Xiongwei Song <sxwjean@gmail.com>
To: Hsin-Yi Wang <hsinyi@chromium.org>
Cc: Phillip Lougher <phillip@squashfs.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Xiongwei Song <Xiongwei.Song@windriver.com>,
Zheng Liang <zhengliang6@huawei.com>,
Zhang Yi <yi.zhang@huawei.com>, Hou Tao <houtao1@huawei.com>,
Miao Xie <miaoxie@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm @ kvack . org" <linux-mm@kvack.org>,
"squashfs-devel @ lists . sourceforge . net"
<squashfs-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] Revert "squashfs: provide backing_dev_info in order to disable read-ahead"
Date: Tue, 17 May 2022 17:15:58 +0800 [thread overview]
Message-ID: <CAEVVKH8vOYov+edGWOWbrgi=5UAnNN4FzcAV5i3EVJ8S7_NSDw@mail.gmail.com> (raw)
In-Reply-To: <20220517082650.2005840-2-hsinyi@chromium.org>
On Tue, May 17, 2022 at 4:27 PM Hsin-Yi Wang <hsinyi@chromium.org> wrote:
>
> This reverts commit 9eec1d897139e5de287af5d559a02b811b844d82.
>
> Revert closing the readahead to squashfs since the readahead callback
> for squashfs is implemented.
>
> Suggested-by: Xiongwei Song <sxwjean@gmail.com>
I'd like to use "xiongwei.song@windriver.com" in my tag.
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> ---
> fs/squashfs/super.c | 33 ---------------------------------
> 1 file changed, 33 deletions(-)
>
> diff --git a/fs/squashfs/super.c b/fs/squashfs/super.c
> index 6d594ba2ed28..32565dafa7f3 100644
> --- a/fs/squashfs/super.c
> +++ b/fs/squashfs/super.c
> @@ -29,7 +29,6 @@
> #include <linux/module.h>
> #include <linux/magic.h>
> #include <linux/xattr.h>
> -#include <linux/backing-dev.h>
>
> #include "squashfs_fs.h"
> #include "squashfs_fs_sb.h"
> @@ -113,24 +112,6 @@ static const struct squashfs_decompressor *supported_squashfs_filesystem(
> return decompressor;
> }
>
> -static int squashfs_bdi_init(struct super_block *sb)
> -{
> - int err;
> - unsigned int major = MAJOR(sb->s_dev);
> - unsigned int minor = MINOR(sb->s_dev);
> -
> - bdi_put(sb->s_bdi);
> - sb->s_bdi = &noop_backing_dev_info;
> -
> - err = super_setup_bdi_name(sb, "squashfs_%u_%u", major, minor);
> - if (err)
> - return err;
> -
> - sb->s_bdi->ra_pages = 0;
> - sb->s_bdi->io_pages = 0;
> -
> - return 0;
> -}
>
> static int squashfs_fill_super(struct super_block *sb, struct fs_context *fc)
> {
> @@ -146,20 +127,6 @@ static int squashfs_fill_super(struct super_block *sb, struct fs_context *fc)
>
> TRACE("Entered squashfs_fill_superblock\n");
>
> - /*
> - * squashfs provides 'backing_dev_info' in order to disable read-ahead. For
> - * squashfs, I/O is not deferred, it is done immediately in read_folio,
> - * which means the user would always have to wait their own I/O. So the effect
> - * of readahead is very weak for squashfs. squashfs_bdi_init will set
> - * sb->s_bdi->ra_pages and sb->s_bdi->io_pages to 0 and close readahead for
> - * squashfs.
> - */
> - err = squashfs_bdi_init(sb);
> - if (err) {
> - errorf(fc, "squashfs init bdi failed");
> - return err;
> - }
> -
> sb->s_fs_info = kzalloc(sizeof(*msblk), GFP_KERNEL);
> if (sb->s_fs_info == NULL) {
> ERROR("Failed to allocate squashfs_sb_info\n");
> --
> 2.36.0.550.gb090851708-goog
>
>
next prev parent reply other threads:[~2022-05-17 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 8:26 [PATCH v2 0/3] Implement readahead for squashfs Hsin-Yi Wang
2022-05-17 8:26 ` [PATCH v2 1/3] Revert "squashfs: provide backing_dev_info in order to disable read-ahead" Hsin-Yi Wang
2022-05-17 9:15 ` Xiongwei Song [this message]
2022-05-17 8:26 ` [PATCH v2 2/3] squashfs: always build "file direct" version of page actor Hsin-Yi Wang
2022-05-17 8:26 ` [PATCH v2 3/3] squashfs: implement readahead Hsin-Yi Wang
2022-05-17 9:16 ` Xiongwei Song
2022-05-19 7:56 ` Hsin-Yi Wang
2022-05-19 8:09 ` Hsin-Yi Wang
2022-05-20 3:02 ` Phillip Lougher
2022-05-20 7:38 ` Hsin-Yi Wang
2022-05-20 20:21 ` Phillip Lougher
2022-05-23 7:00 ` Hsin-Yi Wang
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='CAEVVKH8vOYov+edGWOWbrgi=5UAnNN4FzcAV5i3EVJ8S7_NSDw@mail.gmail.com' \
--to=sxwjean@gmail.com \
--cc=Xiongwei.Song@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=houtao1@huawei.com \
--cc=hsinyi@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miaoxie@huawei.com \
--cc=phillip@squashfs.org.uk \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=willy@infradead.org \
--cc=yi.zhang@huawei.com \
--cc=zhengliang6@huawei.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 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).