> This seems to be doing what PAGG does (or should do).
I'm not a PAGG expert, so my questions here are not definitive of what
PAGG does or should do.
However, I will confess to some puzzlement over your suggestion that
such is the same as it is for the kernel monitor described in your note.
I certainly see _some_ commonality in mechanisms, with one or another
flavor of flexible and dynamically modified hooks in places such as fork
But other mechanisms, such as filtering and queueing of events for
transmission to a user deamon, don't match anything I was aware of in
And other mechanisms that I thought existed in PAGG, such as a sort of
named callout to code in loadable kernel modules to be executed at such
hooks, and such as some way of grouping related tasks which are to
receive common treatment, I didn't notice, in my cursory reading, of
this monitor mechanism.
And I am at a loss to guess what you know that PAGG "should" do distinct
from what it does.
Perhaps it would help if you stated explicitly what you understand PAGG
does, and should do, rather than leaving that as unspoken implication.
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@xxxxxxx> 1.650.933.1373