Author pablogsal
Recipients John Jones, alex, benjamin.peterson, dhduvall, gennad, gregory.p.smith, martin.panter, miss-islington, ned.deily, neologix, pablogsal, serhiy.storchaka, vstinner
Date 2018-05-14.15:58:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526313520.99.0.682650639539.issue20104@psf.upfronthosting.co.za>
In-reply-to
Content
Regarding the rationale for when posix_spawn can be useful (from the RATIONALE section of the man page):

The posix_spawn() function and its close relation posix_spawnp() have been introduced to overcome the following perceived difficulties with fork(): the fork() function is difficult or impossible to implement without swapping or dynamic address translation.

Swapping is generally too slow for a realtime environment.

Dynamic address translation is not available everywhere that POSIX might be useful.

Processes are too useful to simply option out of POSIX whenever it must run without address translation or other MMU services.

Thus, POSIX needs process creation and file execution primitives that can be efficiently implemented without address translation or other MMU services.
History
Date User Action Args
2018-05-14 16:17:16pablogsalunlinkissue20104 messages
2018-05-14 15:58:41pablogsalsetrecipients: + pablogsal, gregory.p.smith, vstinner, benjamin.peterson, ned.deily, alex, dhduvall, neologix, gennad, martin.panter, serhiy.storchaka, John Jones, miss-islington
2018-05-14 15:58:40pablogsalsetmessageid: <1526313520.99.0.682650639539.issue20104@psf.upfronthosting.co.za>
2018-05-14 15:58:40pablogsallinkissue20104 messages
2018-05-14 15:58:40pablogsalcreate