public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yi Yang <yang.y.yi@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, akpm@osdl.org, johnpol@2ka.mipt.ru,
	matthltc@us.ibm.com
Subject: Re: Connector: Filesystem Events Connector v3
Date: Sat, 25 Mar 2006 13:37:45 +0800	[thread overview]
Message-ID: <4424D729.6040602@gmail.com> (raw)
In-Reply-To: <1143210312.2882.72.camel@laptopd505.fenrus.org>

Arjan van de Ven 写道:
> 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.
>   
sending to userspace is common for audit and the filesystem events
connector,
audit has many branches to process before sending audit result, it is
real big
overhead.
>
>
>   


  reply	other threads:[~2006-03-25  5:37 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 [this message]
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=4424D729.6040602@gmail.com \
    --to=yang.y.yi@gmail.com \
    --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 \
    /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