From: Rik van Riel <riel@redhat.com>
To: Simo Sorce <ssorce@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
john@johnmccutchan.com, rlove@rlove.org,
Eric Paris <eparis@redhat.com>, Jeff Layton <jlayton@redhat.com>
Subject: Re: [PATCH] inotify: add hook to catch fsync/msync events
Date: Mon, 30 Mar 2009 14:17:27 -0400 [thread overview]
Message-ID: <49D10CB7.7020805@redhat.com> (raw)
In-Reply-To: <1238434567.3597.31.camel@localhost.localdomain>
Simo Sorce wrote:
> An external application that is interested to know if a database file has
> changed (in a meaningful way), would have no other way but to listen for
> IN_SYNC events.
Normal inotify tells the listener "something changed".
IN_SYNC tells the listeners "there is new, useful data".
Because this new inotify signal gives the listener more
useful information than the existing inotify paths, at
least for your use case, I believe the patch makes
perfect sense and should be merged.
> Signed-off-by: Simo Sorce <ssorce@redhat.com>
Reviewed-by: Rik van Riel <riel@redhat.com>
--
All rights reversed.
prev parent reply other threads:[~2009-03-30 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 17:36 [PATCH] inotify: add hook to catch fsync/msync events Simo Sorce
2009-03-30 18:17 ` Rik van Riel [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=49D10CB7.7020805@redhat.com \
--to=riel@redhat.com \
--cc=eparis@redhat.com \
--cc=jlayton@redhat.com \
--cc=john@johnmccutchan.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=ssorce@redhat.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;
as well as URLs for NNTP newsgroup(s).