Subject: Re: [2.6.16 PATCH] Connector: Filesystem Events Connector v3
From: Arjan van de Ven <arjan@infradead.org>
To: Yi Yang <yang.y.yi@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>,
       Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
       Matt Helsley <matthltc@us.ibm.com>
In-Reply-To: <4423673C.7000008@gmail.com>
References: <4423673C.7000008@gmail.com>
Content-Type: text/plain
Date: Fri, 24 Mar 2006 07:59:01 +0100
Message-Id: <1143183541.2882.7.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 953
Lines: 23


> It is also never redundant functionality of audit subsystem, if enable 
> audit option, audit subsystem will audit all the syscalls, so it adds 
> big overhead for the whole system, 

this is not true

> but Filesystem Event Connector just
>  concerns those operations related to the filesystem, so it has little
>  overhead, moreover, audit subsystem is a complicated function block, 
> it not only sends audit results to netlink interface, but also send 
> them to klog or syslog, so it will add big overhead. you can look File
>  Event Connector as subset of audit subsystem, but File Event Connector
>  is a very very lightweight subsystem.

then make the syslog part optional.. if it's not already!


-
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/