From: Jens Axboe <axboe@kernel.dk>
To: Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH v2] fsnotify: optimize the case of no content event watchers
Date: Thu, 11 Jan 2024 09:46:08 -0700 [thread overview]
Message-ID: <7be392ea-a622-4195-980f-9edc5497802b@kernel.dk> (raw)
In-Reply-To: <20240111152233.352912-1-amir73il@gmail.com>
On 1/11/24 8:22 AM, Amir Goldstein wrote:
> Jens,
>
> Can you take v2 for a spin with your workloads?
Still looks good from a performance POV, same as v1. No 6-8% of fsnotify
and parent CPU wastage.
--
Jens Axboe
next prev parent reply other threads:[~2024-01-11 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 15:22 [RFC][PATCH v2] fsnotify: optimize the case of no content event watchers Amir Goldstein
2024-01-11 16:46 ` Jens Axboe [this message]
2024-01-12 11:09 ` Jan Kara
2024-01-12 13:00 ` Amir Goldstein
2024-01-12 13:58 ` Jens Axboe
2024-01-12 14:11 ` Jens Axboe
2024-01-12 14:36 ` Amir Goldstein
2024-01-15 18:37 ` Jan Kara
2024-01-15 19:42 ` Amir Goldstein
2024-01-15 20:48 ` Jens Axboe
2024-01-15 16:11 ` Jan Kara
2024-01-15 16:14 ` Jens Axboe
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=7be392ea-a622-4195-980f-9edc5497802b@kernel.dk \
--to=axboe@kernel.dk \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).