From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, Jan Kara <jack@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: [LSF/MM TOPIC ATTEND] thawing the fsnotify subsyetm
Date: Fri, 20 Jan 2017 09:47:51 +0100 [thread overview]
Message-ID: <20170120084751.GB14115@quack2.suse.cz> (raw)
In-Reply-To: <CAOQ4uxh9ZbSfO-6V6cYNbNd2eBvVV6MxBCnpSzyp3-zKrYeWWw@mail.gmail.com>
On Thu 19-01-17 16:28:09, Amir Goldstein wrote:
> My employer has a use case of watching file system changes
> over millions of directories.
>
> It so happens that the same product (cloud sync) also runs on
> Windows and on MacOS. both OS have a scalable API to monitor
> file systems changes over millions of directories.
>
> Since the product requires being notified on filename events
> (e.g. create/delete/rename), the only available option on Linux is
> inotify, but inotify does not scale well to millions of directories
> use case and not a the right tool for the job in general.
>
> For that purpose, I implemented fanotify super block watch [1],
> to be able to:
> 1. report filename events
> 2. watch over file system root (as opposed to mount point)
> 3. report event information using struct file_handle,
> instead of keeping open file descriptor per event
Yeah, I think this would be worth a discussion. I've got other requests for
similar functionality so Amir is not the only one with the needs. But given
how unsuccessful we have been with file change notification API in the past
I'm very conservative about its extensions and would prefer to have wider
discussion about this.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2017-01-20 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 14:28 [LSF/MM TOPIC ATTEND] thawing the fsnotify subsyetm Amir Goldstein
2017-01-20 8:47 ` Jan Kara [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=20170120084751.GB14115@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).