All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <yi1.lai@intel.com>
To: Hengyu Liang <hengyul@cs.unc.edu>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, David Sterba <dsterba@suse.com>,
	Qu Wenruo <wqu@suse.com>, Filipe Manana <fdmanana@suse.com>,
	linux-btrfs@vger.kernel.org, yi1.lai@intel.com
Subject: [linus:master] [btrfs]  16b8f07d1e: stress-ng.inode-flags.ops_per_sec 89.3% improvement
Date: Thu, 19 Nov 2026 16:01:50 +0800	[thread overview]
Message-ID: <202611190824.7d8fe82f-lkp@intel.com> (raw)



Hello,

kernel test robot noticed a 89.3% improvement of stress-ng.inode-flags.ops_per_sec on:


commit: 16b8f07d1ed50d4a8da468b56484873784dd8f4a ("btrfs: fix chattr failing on nodatasum files that have the compress flag")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) (Sapphire Rapids) with 128G memory
parameters:

	nr_threads: 100%
	disk: 1SSD
	testtime: 60s
	fs: btrfs
	test: inode-flags
	cpufreq_governor: performance


Details are as below:
-------------------------------------------------------------------------------------------------->

The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261119/202611190824.7d8fe82f-lkp@intel.com

=========================================================================================
compiler/cpufreq_governor/disk/fs/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
  gcc-14/performance/1SSD/btrfs/x86_64-rhel-9.4/100%/debian-13-x86_64-20250902.cgz/lkp-spr-2sp3/inode-flags/stress-ng/60s

commit: 
  58e844c3ba ("btrfs: fix use-after-free on quota enable allocation failure")
  16b8f07d1e ("btrfs: fix chattr failing on nodatasum files that have the compress flag")

58e844c3ba387ceb 16b8f07d1ed50d4a8da468b5648 
---------------- --------------------------- 
         %stddev     %change         %stddev
             \          |                \  
    204635           +89.2%     387239        stress-ng.inode-flags.ops
      3409           +89.3%       6454        stress-ng.inode-flags.ops_per_sec
   4400053 ± 12%     -96.0%     175237 ±  5%  stress-ng.time.file_system_outputs
     30530 ±  3%   +2174.3%     694344        stress-ng.time.involuntary_context_switches
    181230 ±  2%      +4.4%     189263        stress-ng.time.minor_page_faults
      1174         +1503.6%      18832        stress-ng.time.percent_of_cpu_this_job_got
    673.93         +1574.9%      11287        stress-ng.time.system_time
  23712987           -60.1%    9463627        stress-ng.time.voluntary_context_switches


Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki



                 reply	other threads:[~2026-11-19  8:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202611190824.7d8fe82f-lkp@intel.com \
    --to=yi1.lai@intel.com \
    --cc=dsterba@suse.com \
    --cc=fdmanana@suse.com \
    --cc=hengyul@cs.unc.edu \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=wqu@suse.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.