pagg
[Top] [All Lists]

Re: [PATCH 1/3] Process Notification / pnotify

To: Erik Jacobson <erikj@xxxxxxx>, Matthew Helsley <matthltc@xxxxxxxxxx>
Subject: Re: [PATCH 1/3] Process Notification / pnotify
From: Paul Jackson <pj@xxxxxxx>
Date: Mon, 3 Oct 2005 12:49:18 -0700
Cc: linux-kernel@xxxxxxxxxxxxxxx, pagg@xxxxxxxxxxx
In-reply-to: <20051003184644.GA19106@sgi.com>
Organization: SGI
References: <20051003184644.GA19106@sgi.com>
Sender: pagg-bounce@xxxxxxxxxxx
Hmmm ... I notice with interest two notification patches posted in
the last few days to lkml:

  Matthew Helsley's Process Events Connector (posted 28 Sep 2005)
  Erik Jacobson's pnotify (posted 3 Oct 2005)

I suspect Matthew and Erik will both instantly hate me for asking, but
does it make sense to integrate these two?

If I understand these two proposals correctly:

    Helsley adds hooks in fork, exec, id change, and exit, to pass
    events to userspace.

    Jacobson adds hooks in fork, exec and exit, to pass events to
    kernel routines and loadable modules.

Perhaps, just brainstorming here, it would make sense for Halsley to
register with pnotify instead of adding his own hooks in parallel.
This presumes that pnotify is accepted into the kernel, and that
pnotify adds the id change hook that Helsley requires.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@xxxxxxx> 1.925.600.0401

<Prev in Thread] Current Thread [Next in Thread>