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>
Subject: Re: [2.6.16 PATCH] Connector: Filesystem Events Connector v3
Date: Fri, 24 Mar 2006 07:59:01 +0100 [thread overview]
Message-ID: <1143183541.2882.7.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4423673C.7000008@gmail.com>
> 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!
next prev parent reply other threads:[~2006-03-24 6:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 3:27 Yi Yang
2006-03-24 6:59 ` Arjan van de Ven [this message]
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
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=1143183541.2882.7.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®