[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whSncSTE_Q0as-d989L_niJ6=ViwaDoOK6gTcWHNPkp7w@mail.gmail.com>
Date: Thu, 6 Feb 2025 12:45:14 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: Amir Goldstein <amir73il@...il.com>, oe-lkp@...ts.linux.dev, lkp@...el.com,
linux-kernel@...r.kernel.org, Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org
Subject: Re: [linus:master] [fsnotify] a94204f4d4: stress-ng.timerfd.ops_per_sec
7.0% improvement
On Wed, 5 Feb 2025 at 00:09, kernel test robot <oliver.sang@...el.com> wrote:
>
> kernel test robot noticed a 7.0% improvement of stress-ng.timerfd.ops_per_sec on:
I have no idea what the heck that benchmark does, but I am happy to
see that this whole patch series did actually end up improving on the
whole fsnotify cost that I was ranting about in the original
submission.
Obviously this load doesn't actually do the new pre-event hooks, so it
seems to be all just about how fsnotify_file_area_perm() (or some
other fsnotify hook in the normal read() path) now isn't the
unconditional pig that it used to be.
I don't see how that would be worth 7%, but I'll happily take it.
Linus
Powered by blists - more mailing lists