Re: [patch 1/2] fork_connector: add a fork connector

[Ram]

On Mon, 2005-03-21 at 04:48, Guillaume Thouvenin wrote:
> ChangeLog:
> 
>   - Remove the global cn_fork_lock and replace it by a per CPU 
>     counter. 
>   - The processor ID has been added in the data part of the message.
>     Thus datas sent in a message are: "CPU_ID PARENT_PID CHILD_PID"
> 
>   Those modifications were done to be more scalable because, as
> mentioned by Jesse Barnes, the global cn_fork_lock won't work well on a
> large CPU system.
> 
>   This patch applies to 2.6.11-mm4.
Guillaume,

     If a bunch of applications are listening for fork events, 
     your patch allows any application to turn off the 
     fork event notification?  Is this the right behavior?

     Should'nt it turn off the fork-event notification when 
     the number of listeners become zero?
  
RP


 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/