Hi! > > > I think you're right in scenario with single CPU. > > > In theory, is it possible that set_affinity() would be dummy, and one of > > > ncpu-1 children running with max FIFO priority would preempt parent > > > allowing test_process() to run before its priority is changed? > > > > Aren't the child proceesses forked with the same priority as the parent? > > In this case they shouldn't get executed for the same reason unless they > > are migrated other CPUs. But yes then it's a kind of unpredictable which > > is the reason we have the affinity call there. > > Would you prefer I rewrite that comment? Or are you OK with the patch as it > is?
It would be better to make the comment more clear. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
