Hi Daeho,
Could you please clean up a bit on this patch, we can wrap vm_map_ram
loop logic into f2fs_vmap() as below:
f2fs_vmap()
{
for (i = 0; i < MAX_VMAP_RETRIES; i++) {
cc->cbuf = vm_map_ram(cc->cpages, cc->nr_cpages, -1);
if (cc->cbuf)
On 2020/8/12 13:17, Daeho Jeong wrote:
From: Daeho Jeong
By profiling f2fs compression works, I've found vmap() callings have
unexpected hikes in the execution time in our test environment and
those are bottlenecks of f2fs decompression path. Changing these with
vm_map_ram(), we can enhance
On Wed, Aug 12, 2020 at 02:17:11PM +0900, Daeho Jeong wrote:
> From: Daeho Jeong
>
> By profiling f2fs compression works, I've found vmap() callings have
> unexpected hikes in the execution time in our test environment and
> those are bottlenecks of f2fs decompression path. Changing these with
>
From: Daeho Jeong
By profiling f2fs compression works, I've found vmap() callings have
unexpected hikes in the execution time in our test environment and
those are bottlenecks of f2fs decompression path. Changing these with
vm_map_ram(), we can enhance f2fs decompression speed pretty much.
4 matches
Mail list logo
