Subject: Re: Connector: Filesystem Events Connector v3
From: Arjan van de Ven <arjan@infradead.org>
To: yang.y.yi@gmail.com
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org,
       akpm@osdl.org, johnpol@2ka.mipt.ru, matthltc@us.ibm.com
In-Reply-To: <4c4443230603240614m5f495340y9dc6ccc45e1e45b4@mail.gmail.com>
References: <4423673C.7000008@gmail.com>
	 <1143183541.2882.7.camel@laptopd505.fenrus.org>
	 <20060323.230649.11516073.davem@davemloft.net>
	 <4c4443230603240614m5f495340y9dc6ccc45e1e45b4@mail.gmail.com>
Content-Type: text/plain
Date: Fri, 24 Mar 2006 15:25:11 +0100
Message-Id: <1143210312.2882.72.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1208
Lines: 29

On Fri, 2006-03-24 at 22:14 +0800, yang.y.yi@gmail.com wrote:
> On 3/24/06, 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.
> >
> > Audit just has way too much crap in it, and it's so much nicer to have
> > tiny modules that are optimized for specific areas of activity over
> > something like audit that tries to do everything.
> >
> the filesystem events connector is small and has low overhead, it only
> focuses on
>  activities in the filesystem

... so much that it's not useful for antivirus at least.
And your claim that audit has big overhead.. can you substantiate that?
I mean, this code has big overhead too in principle, the biggest
bottleneck is the sending-to-userspace, and that's the same in both.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/