Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Leo Martins <loemra.dev@gmail.com>
To: kernel test robot <oliver.sang@intel.com>, oe-lkp@lists.linux.dev
Cc: lkp@intel.com, linux-btrfs@vger.kernel.org, kernel-team@fb.com,
	David Sterba <dsterba@suse.com>
Subject: Re: [linux-next:master] [btrfs]  9a8eec6165:  fio.write_iops 22.6% regression
Date: Wed,  1 Jul 2026 16:44:11 -0700	[thread overview]
Message-ID: <20260701234412.4048647-1-loemra.dev@gmail.com> (raw)
In-Reply-To: <202603112240.f7605968-lkp@intel.com>

Hi Oliver,

Thanks for the report. I'm aware of this regression and the cause is
understood: the flagged commit adds a per-COW xarray store on every
COW'd metadata block, and on this single-task 4k randwrite ftruncate
workload that store is what costs the write_iops.

A fix has been posted to linux-btrfs that replaces the xarray with a
non-allocating fixed inline buffer and recovers the lost throughput:

  "btrfs: replace writeback inhibition xarray with a fixed inline buffer"

It carries the Reported-by and Closes tags pointing at this report.

Thanks,
Leo

  reply	other threads:[~2026-07-01 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 14:36 [linux-next:master] [btrfs] 9a8eec6165: fio.write_iops 22.6% regression kernel test robot
2026-07-01 23:44 ` Leo Martins [this message]
2026-07-02  1:55   ` Oliver Sang

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=20260701234412.4048647-1-loemra.dev@gmail.com \
    --to=loemra.dev@gmail.com \
    --cc=dsterba@suse.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox