[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introduce posix_spawn
From: |
Bruno Haible |
Subject: |
Re: Introduce posix_spawn |
Date: |
Sat, 08 Sep 2018 00:06:37 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-134-generic; KDE/5.18.0; x86_64; ; ) |
Eric Blake wrote:
> Although it gets prohibitively expensive in a multi-threaded process to
> ensure proper locking between all threads that might want to use
> posix_spawn
Why locking? posix_spawn uses fork() - the vfork() optimization is not
possible in the case when there are file actions -, which creates a
child process with a single thread. So, in the child, there are no
other threads until the exec() call, and the condition variables,
mutexes, etc. are just inactive memory regions.
Bruno
- RE: Introduce posix_spawn, (continued)
- RE: Introduce posix_spawn, Tavian Barnes, 2018/09/06
- Re: Introduce posix_spawn, Eric Blake, 2018/09/07
- Re: Introduce posix_spawn, Eric Blake, 2018/09/07
- Re: Introduce posix_spawn, Barath Aron, 2018/09/07
- Re: Introduce posix_spawn, Eric Blake, 2018/09/07
- Re: Introduce posix_spawn,
Bruno Haible <=
- Re: Introduce posix_spawn, Eric Blake, 2018/09/07
- Re: Introduce posix_spawn, Bernhard Voelker, 2018/09/08
- Re: Introduce posix_spawn, Eric Blake, 2018/09/10
- Re: posix_spawn_file_actions_addchdir, Bruno Haible, 2018/09/07
- Re: posix_spawn_file_actions_addchdir, Eric Blake, 2018/09/07
- Re: posix_spawn_file_actions_addchdir, Bruno Haible, 2018/09/07
Re: Introduce posix_spawn, Tavian Barnes, 2018/09/10