From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
yang.y.yi@gmail.com, linux-kernel@vger.kernel.org,
matthltc@us.ibm.com
Subject: Re: [2.6.16 PATCH] Connector: Filesystem Events Connector v3
Date: Fri, 24 Mar 2006 11:16:53 +0300 [thread overview]
Message-ID: <20060324081652.GD5426@2ka.mipt.ru> (raw)
In-Reply-To: <1143188094.2882.22.camel@laptopd505.fenrus.org>
On Fri, Mar 24, 2006 at 09:14:53AM +0100, Arjan van de Ven (arjan@infradead.org) wrote:
> On Fri, 2006-03-24 at 11:08 +0300, Evgeniy Polyakov wrote:
> > On Thu, Mar 23, 2006 at 11:23:45PM -0800, Andrew Morton (akpm@osdl.org) wrote:
> > > "David S. Miller" <davem@davemloft.net> wrote:
> > > >
> > > > From: Arjan van de Ven <arjan@infradead.org>
> > > > Date: Fri, 24 Mar 2006 07:59:01 +0100
> > > >
> > > > > then make the syslog part optional.. if it's not already!
> > > >
> > > > Regardless I still think the filesystem events connector is a useful
> > > > facility.
> > >
> > > Why's that?
> > >
> > > (I'd viewed it as a fun thing, but I haven't really seen much pull for it,
> > > and the scalability issues in there aren't trivial).
> >
> > This module uses ratelimiting of event generation, so it will not hurt
> > performance, but probably this should be somehow tuned from userspace.
>
>
> .. so it has become unreliable for any kind of real use that depends on
> getting complete events. Such as virus scanning or updatedb etc
That is why it should be tunable.
Everything has a price.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2006-03-24 8:17 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 [this message]
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
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=20060324081652.GD5426@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--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