From: Andrew Morton <akpm@osdl.org>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: linux-kernel@vger.kernel.org, gh@us.ibm.com,
guillaume.thouvenin@bull.net, elsa-devel@lists.sourceforge.net
Subject: Re: [RFC][PATCH 2.6.11-rc3-mm1] Relay Fork Module
Date: Mon, 7 Feb 2005 15:46:23 -0800 [thread overview]
Message-ID: <20050207154623.33333cda.akpm@osdl.org> (raw)
In-Reply-To: <1107786245.9582.27.camel@frecb000711.frec.bull.fr>
Guillaume Thouvenin <guillaume.thouvenin@bull.net> wrote:
>
> Hello,
>
> This module sends a signal to one or several processes (in user
> space) when a fork occurs in the kernel. It relays information about
> forks (parent and child pid) to a user space application.
>
> ...
> This patch is used by the Enhanced Linux System Accounting tool that
> can be downloaded from http://elsa.sf.net
So this permits ELSA to maintain a complete picture of the process/thread
hierarchy? I guess that fits into the "do it in userspace" mantra -
certainly hooking into fork() is a minimal way of doing this, although I
wonder what the limitations are.
Implementation-wise: there's a lot of code there and the interface is a bit
awkward. Why not just feed that kobject you have there into
kobject_uevent()?
next prev parent reply other threads:[~2005-02-07 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 14:24 Guillaume Thouvenin
2005-02-07 23:46 ` Andrew Morton [this message]
2005-02-08 8:34 ` Guillaume Thouvenin
2005-02-11 8:11 ` [RFC][PATCH 2.6.11-rc3-mm2] " Guillaume Thouvenin
2005-02-11 8:54 ` Andrew Morton
2005-02-11 12:32 ` Guillaume Thouvenin
2005-02-11 15:08 ` Guillaume Thouvenin
2005-02-11 19:11 ` Greg KH
2005-02-14 8:26 ` Guillaume Thouvenin
2005-02-14 17:41 ` Greg KH
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=20050207154623.33333cda.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=guillaume.thouvenin@bull.net \
--cc=linux-kernel@vger.kernel.org \
/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®