mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Murphy" <lists@colorremedies.com>
To: "David Sterba" <dsterba@suse.cz>, "Qu WenRuo" <wqu@suse.com>
Cc: "kernel test robot" <oliver.sang@intel.com>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"David Sterba" <dsterba@suse.com>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: [linus:master] [btrfs] bddf57a707: stress-ng.sync-file.ops_per_sec 44.2% regression
Date: Thu, 04 Sep 2025 13:07:44 -0400	[thread overview]
Message-ID: <7302d357-b42f-4874-af59-43ad03a0b47f@app.fastmail.com> (raw)
In-Reply-To: <20250904143415.GL5333@suse.cz>



On Thu, Sep 4, 2025, at 10:34 AM, David Sterba wrote:
> On Wed, Sep 03, 2025 at 06:18:01PM +0930, Qu Wenruo wrote:
>> This doesn't sound sane to me.
>> 
>> The two commits are only affecting btrfs mounting/unmounting, I can not 
>> make any sense on why they would affect performance.
>> 
>> Or does stress-ng doing a lot of mounting/unmounting?
>
> Yeah, unless there's some indirect way how mount affects the tests the
> numbers do not match the identified patches. The difference is roughly
> consistent in all the stats to be about 40% less so it's like it's doing
> half of the work. Delayed device opening does not explain that.

Does the test run on qemu/kvm? Could cache mode and host workload affect the result?

If it were unsafe mode, the guest very quickly thinks the write is on stable media even though the host can significantly delay writing to stable media. Whereas directsync mode might be really slow since the host must commit to stable media before the guest sees it as on stable media.


-- 
Chris Murphy

      reply	other threads:[~2025-09-04 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03  8:44 kernel test robot
2025-09-03  8:48 ` Qu Wenruo
2025-09-04 14:34   ` David Sterba
2025-09-04 17:07     ` Chris Murphy [this message]

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=7302d357-b42f-4874-af59-43ad03a0b47f@app.fastmail.com \
    --to=lists@colorremedies.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®