All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@engr.sgi.com>
To: Guillaume Thouvenin <Guillaume.Thouvenin@Bull.net>
Cc: Christoph Hellwig <hch@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Erik Jacobson <erikj@dbear.engr.sgi.com>
Subject: Re: [PATCH 2.6.9] fork: add a hook in do_fork()
Date: Tue, 23 Nov 2004 11:31:56 -0800	[thread overview]
Message-ID: <41A3902C.60004@engr.sgi.com> (raw)
In-Reply-To: <1101202407.6210.87.camel@frecb000711.frec.bull.fr>

This is great!

We have one more user of PAGG! :)

Happy Thanksgiving,
  - jay


Guillaume Thouvenin wrote:
> On Tue, 2004-11-23 at 09:03 +0000, Christoph Hellwig wrote:
> 
>>On Tue, Nov 23, 2004 at 07:03:17AM +0100, Guillaume Thouvenin wrote:
>>
>>>   For a module, I need to execute a function when a fork occurs. My
>>>solution is to add a pointer to a function (called fork_hook) in the
>>>do_fork() and if this pointer isn't NULL, I call the function. To update
>>>the pointer to the function I export a symbol (called trace_fork) that
>>>defines another function with two parameters (the hook and an
>>>identifier). This function provides a simple mechanism to manage access
>>>to the fork_hook variable.
>>>
>>
>>Use SGI's PAGG patches if you want such hooks.  Also this is clearly
>>a _GPL export.
> 
> 
> PAGG is more intrusive than my patch due to the management of groups of
> processes. This hook in the fork allows me to provide a solution to do
> per-group accounting with a module. If PAGG is added in the Linux Kernel
> Tree it could be the solution, you are right. 
> 
> Guillaume 
> 


  reply	other threads:[~2004-11-23 19:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  6:03 [PATCH 2.6.9] fork: add a hook in do_fork() Guillaume Thouvenin
2004-11-23  8:06 ` Greg KH
2004-11-23  8:56   ` Guillaume Thouvenin
2004-11-23 10:09     ` Guillaume Thouvenin
2004-11-23 14:14   ` Guillaume Thouvenin
2004-11-23 21:51     ` Chris Wright
2004-11-24  8:14       ` Guillaume Thouvenin
2004-11-23  9:03 ` Christoph Hellwig
2004-11-23  9:33   ` Guillaume Thouvenin
2004-11-23 19:31     ` Jay Lan [this message]
2004-11-23  9:59 ` Hua Zhong
2004-11-23 10:14   ` Guillaume Thouvenin
2004-11-23 13:55 ` Jan Engelhardt

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=41A3902C.60004@engr.sgi.com \
    --to=jlan@engr.sgi.com \
    --cc=Guillaume.Thouvenin@Bull.net \
    --cc=akpm@osdl.org \
    --cc=erikj@dbear.engr.sgi.com \
    --cc=hch@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.