[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <nfqwkcdbd5xawykrtb5nrhvmpfimtry6qyuig5p7qmlehc7itl@utic4l437gwn>
Date: Fri, 3 Oct 2025 15:38:28 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: Christoph Hellwig <hch@....de>
Cc: kernel test robot <oliver.sang@...el.com>,
Dave Chinner <dchinner@...hat.com>, oe-lkp@...ts.linux.dev, lkp@...el.com,
linux-kernel@...r.kernel.org, Carlos Maiolino <cem@...nel.org>, Jan Kara <jack@...e.cz>,
linux-xfs@...r.kernel.org
Subject: Re: [linus:master] [xfs] c91d38b57f: stress-ng.chown.ops_per_sec
70.2% improvement
On Fri, Oct 03, 2025 at 09:56:15AM +0200, Christoph Hellwig wrote:
> 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.
>
According to my strace there is no fsync, instead all of the worker
threads are issuing chown, lchown and fchown on the same inode.
As far as *benchmarking* goes this is useless.
Note stress-ng does not claim to be a benchmarking suite, but a stress
test suite which can also report ops/s for whatever it did.
This bit does not look particularly useful for stress testing either tbh.
Powered by blists - more mailing lists