[659] Still fork even if jobs == 1.
Michael G Schwern
schwern at pobox.com
Wed Oct 3 00:35:06 BST 2007
Andy Armstrong wrote:
> On 3 Oct 2007, at 00:12, Michael G Schwern wrote:
>>> Still fork even if jobs == 1.
>>> With jobs == 0 it executes the forking code path but no forking
>>> takes place inside Parallel::Iterator.
>> So --fork -j1 means what processes are doing what again?
>
> Jobs == 0 : no forking
> Jobs == 1 .. n : fork that many workers
Sorry, I'm still confused. I'm a bit lost in how the new parallel
implementation works. What part is forking? I presumed the TAP parser is
forking but then I don't understand why having one fork is useful.
--
Whip me, beat me, make my code compatible with VMS!
More information about the tapx-dev
mailing list