From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: Dave Chinner <dchinner@redhat.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, Carlos Maiolino <cem@kernel.org>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org
Subject: Re: [linus:master] [xfs] c91d38b57f: stress-ng.chown.ops_per_sec 70.2% improvement
Date: Fri, 3 Oct 2025 09:56:15 +0200 [thread overview]
Message-ID: <20251003075615.GA13238@lst.de> (raw)
In-Reply-To: <202510020917.2ead7cfe-lkp@intel.com>
On Thu, Oct 02, 2025 at 04:11:29PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed a 70.2% improvement of stress-ng.chown.ops_per_sec on:
I wonder what stress-ng shown is doing, because unless it is mixing fsync
and ilock-heavy operations on the same node this would be highly
unexpected.
next prev parent reply other threads:[~2025-10-03 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 8:11 [linus:master] [xfs] c91d38b57f: stress-ng.chown.ops_per_sec 70.2% improvement kernel test robot
2025-10-03 7:56 ` Christoph Hellwig [this message]
2025-10-03 13:38 ` Mateusz Guzik
2025-10-05 11:54 ` Dave Chinner
2025-10-07 6:44 ` Christoph Hellwig
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=20251003075615.GA13238@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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