On 3/8/07, Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote: > On Wed, Mar 07, 2007 at 12:50:03PM -0800, Paul Menage wrote: > > The callback mutex (which is what container_lock() actually locks) is > > also used to synchronize fork/exit against subsystem additions, in the > > event that some subsystem has registered fork or exit callbacks. We > > could probably have a separate subsystem_mutex for that instead. > > Why can't manage_mutex itself be used there (to serialize fork/exit callbacks > against modification to hierarchy)?
Because manage_mutex can be held for very long periods of time. I think that a combination of a new lock that's only taken by fork/exit and register_subsys, plus task_lock (which prevents the current task from being moved) would be more lightweight. Paul ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
