On 4/4/07, Paul Menage <[EMAIL PROTECTED]> wrote: > The current code creates such arrays when it needs an atomic snapshot > of the set of tasks in the container (e.g. for reporting them to > userspace or updating the mempolicies of all the tasks in the case of > cpusets). It may be possible to do it by traversing tasklist and > dropping the lock to operate on each task where necessary - I'll take > a look at that.
Just to clarify this - the cases that currently need an array of task pointers *do* already traverse tasklist in order to locate those tasks as needed - its when they want to be able to operate on those tasks outside of the tasklist lock that the array is needed - lock tasklist_lock, fill the array with tasks (with added refcounts), drop tasklist_lock, do stuff. 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
