lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Jan 2021 13:58:18 +0800
From:   Xing Zhengjun <>
To:, kernel test robot <>,
        Josef Bacik <>,
        David Sterba <>,
        René Rebe <>,
        LKML <>,,,,,
Subject: Re: [LKP] Re: [btrfs] e076ab2a2c: fio.write_iops -18.3% regression

On 1/12/2021 11:45 PM, David Sterba wrote:
> On Tue, Jan 12, 2021 at 11:36:14PM +0800, kernel test robot wrote:
>> Greeting,
>> FYI, we noticed a -18.3% regression of fio.write_iops due to commit:
>> commit: e076ab2a2ca70a0270232067cd49f76cd92efe64 ("btrfs: shrink delalloc pages instead of full inodes")
>> master
>> in testcase: fio-basic
>> on test machine: 192 threads Intel(R) Xeon(R) CPU @ 2.20GHz with 192G memory
>> with following parameters:
>> 	disk: 1SSD
>> 	fs: btrfs
>> 	runtime: 300s
>> 	nr_task: 8
>> 	rw: randwrite
>> 	bs: 4k
>> 	ioengine: sync
>> 	test_size: 256g
> Though I do a similar test (emulating bit torrent workload), it's a bit
> extreme as it's 4k synchronous on a huge file. It always takes a lot of
> time but could point out some concurrency issues namely on faster
> devices. There are 8 threads possibly competing for the same inode lock
> or other locks related to it.
> The mentioned commit fixed another perf regression on a much more common
> workload (untgrring files), so at this point drop in this fio workload
> is inevitable.

Do you have a plan to fix it? Thanks.
> _______________________________________________
> LKP mailing list --
> To unsubscribe send an email to

Zhengjun Xing

Powered by blists - more mailing lists