Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: compress: add compress_inode to cache
 compressed blocks
To:     Eric Biggers <ebiggers@kernel.org>
CC:     <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
        <linux-f2fs-devel@lists.sourceforge.net>
References: <20201126103709.80006-1-yuchao0@huawei.com>
 <X7/sCLnVPOjkC9DI@sol.localdomain>
From:   Chao Yu <yuchao0@huawei.com>
Message-ID: <7ecb947e-2f8c-abd7-c116-c82c474fded7@huawei.com>
Date:   Fri, 27 Nov 2020 09:01:47 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <X7/sCLnVPOjkC9DI@sol.localdomain>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2020/11/27 1:55, Eric Biggers wrote:
> 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?

In current implementation, they are decrypted in cache.

Thanks,

> 
> - Eric
> .
>