From: Greg Stark <gsstark@mit.edu>
To: yang.y.yi@gmail.com
Cc: "David S. Miller" <davem@davemloft.net>,
arjan@infradead.org, linux-kernel@vger.kernel.org, akpm@osdl.org,
johnpol@2ka.mipt.ru, matthltc@us.ibm.com
Subject: Re: Connector: Filesystem Events Connector v3
Date: 25 Mar 2006 18:16:32 -0500 [thread overview]
Message-ID: <8764m2i08f.fsf@stark.xeocode.com> (raw)
In-Reply-To: <4c4443230603240614m5f495340y9dc6ccc45e1e45b4@mail.gmail.com>
yang.y.yi@gmail.com writes:
> the filesystem events connector is small and has low overhead, it only
> focuses on activities in the filesystem, so I think it should be an option
> for those users which just concerns events in the filesystem. audit dose do
> this, but it is complicated and overhead is big, I believe the filesystem
> events connector is useful, but it maybe need to be improved further.
Would this be a good tool to tell me why I hear my hard drive stutter
periodically? This is above the regular buffer flushing.
I'm curious what application is causing this file i/o since I have plenty of
free RAM so the only reason it would be hitting disk is if something is
calling fsync gratuitously.
--
greg
next prev parent reply other threads:[~2006-03-25 23:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 3:27 [2.6.16 PATCH] Connector: Filesystem Events Connector v3 Yi Yang
2006-03-24 6:59 ` Arjan van de Ven
2006-03-24 7:06 ` David S. Miller
2006-03-24 7:23 ` Andrew Morton
2006-03-24 7:29 ` David S. Miller
2006-03-24 7:42 ` Andrew Morton
2006-03-24 7:52 ` CaT
2006-03-24 7:55 ` Arjan van de Ven
2006-03-24 8:08 ` Evgeniy Polyakov
2006-03-24 8:14 ` Arjan van de Ven
2006-03-24 8:16 ` Evgeniy Polyakov
2006-03-24 14:20 ` yang.y.yi
2006-03-24 14:14 ` yang.y.yi
2006-03-24 14:25 ` Arjan van de Ven
2006-03-25 5:37 ` Yi Yang
2006-03-25 23:16 ` Greg Stark [this message]
2006-03-26 7:14 ` Benoit Boissinot
2006-03-24 14:24 ` yang.y.yi
2006-03-24 14:28 ` Arjan van de Ven
2006-03-24 15:44 ` James Morris
2006-03-24 21:13 ` Evgeniy Polyakov
2006-03-24 8:05 ` [2.6.16 PATCH] " Evgeniy Polyakov
2006-03-24 8:20 ` David S. Miller
2006-03-24 8:25 ` Evgeniy Polyakov
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=8764m2i08f.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=yang.y.yi@gmail.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