Corinna Vinschen wrote:
> Unfortunately you can't expect any noticable difference on Cygwin by
> using posix_spawn. While Cygwin has a spawn() family of functions, we
> don't (and can't... yet) use them.
>
> The problem is that we don't have a safe way to perform the spawn
> attributes and file actions which are supposed to be performed between
> the fork() and the exec() step when using the spawn() functions. This
> would have to be implemented first.
So, you are saying that on Cygwin, spawnvpe() and friends are fast,
because child_info_spawn::worker ends up calling CreateProcessW rather
immediately? But posix_spawn is slow, because it goes another path,
through fork()?
If that's the case, it might help to look at how I created Gnulib's
posix_spawn for native Windows:
1) Extend the spawnvpe function to a spawnvpech function. It takes
additional arguments
- const char *currdir
- int currdirfd
- HANDLE stdin_handle, HANDLE stdout_handle, HANDLE stderr_handle
(The latter is because the first 3 file descriptors are passed
specially on Windows.)
2) Refactor the guts of spawnvpech, moving as much as possible into
helper functions. In my case, spawnvpech shrunk to only 150 lines
of code.
The helper functions, in the native Windows case, were:
- prepare_spawn
- compose_command
- compose_envblock
- init_inheritable_handles, compose_handles_block,
free_inheritable_handles
- convert_CreateProcess_error
See
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/windows-spawn.h .
I would expect that similar helper functions can be created in
Cygwin.
The "inheritable handles" is a data structure that allows for the
arbitrary reshuffling of file descriptors required by posix_spawn
(the addopen, adddup2, addclose actions), i.e. which does the book-
keeping which HANDLE must in the end be open in the parent and which
must in the end be open in the child, and at which position. While
at the same time optimizing the number of DuplicateHandle calls.
Without this optimization, the code is simpler, but there were many
redundant DuplicateHandle calls.
This data structure is essential for posix_spawn[p] to be multithread-
safe. posix_spawn[p] must not modify the file descriptors of the
parent; instead it has to create the planned file descriptors for the
child in memory.
During this refactoring, it is essential to have a good test suite.
Because when you make a mistake and leave a fd / HANDLE accidentally
open (in the parent or in the child), applications that invoke a pipe
start to hang.
3) With these helper functions, write a new core for posix_spawn[p].
In my case, it was less than 250 lines of code, which is not
straightforward, but also not really hard either.
See https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/spawni.c
lines 610..852.
At this step, you can use Gnulib's test suite for verifying that the new
code works properly.
Hope this helps.
Bruno
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
