From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: compress: add compress_inode to cache compressed blocks
Date: Thu, 26 Nov 2020 09:55:20 -0800 [thread overview]
Message-ID: <X7/sCLnVPOjkC9DI@sol.localdomain> (raw)
In-Reply-To: <20201126103709.80006-1-yuchao0@huawei.com>
On Thu, Nov 26, 2020 at 06:37:09PM +0800, Chao Yu wrote:
> Support to use address space of inner inode to cache compressed block,
> in order to improve cache hit ratio of random read.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
If the file is also encrypted, are the compressed pages that are cached still
encrypted, or are they decrypted?
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: compress: add compress_inode to cache compressed blocks
Date: Thu, 26 Nov 2020 09:55:20 -0800 [thread overview]
Message-ID: <X7/sCLnVPOjkC9DI@sol.localdomain> (raw)
In-Reply-To: <20201126103709.80006-1-yuchao0@huawei.com>
On Thu, Nov 26, 2020 at 06:37:09PM +0800, Chao Yu wrote:
> Support to use address space of inner inode to cache compressed block,
> in order to improve cache hit ratio of random read.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
If the file is also encrypted, are the compressed pages that are cached still
encrypted, or are they decrypted?
- Eric
next prev parent reply other threads:[~2020-11-26 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 10:37 [f2fs-dev] [PATCH v2] f2fs: compress: add compress_inode to cache compressed blocks Chao Yu
2020-11-26 10:37 ` Chao Yu
2020-11-26 17:55 ` Eric Biggers [this message]
2020-11-26 17:55 ` [f2fs-dev] " Eric Biggers
2020-11-27 1:01 ` Chao Yu
2020-11-27 1:01 ` Chao Yu
2020-11-30 18:11 ` Eric Biggers
2020-11-30 18:11 ` Eric Biggers
2020-12-01 2:39 ` Chao Yu
2020-12-01 2:39 ` Chao Yu
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=X7/sCLnVPOjkC9DI@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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 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.