Am 27.10.2021 um 21:55 schrieb Hiebert, Chris <chris.hiebert@xxxxxxxxxxxxxx>:
The pre-start jobs are something I've never looked into, and I'm still hoping you would share those APIs with us.
I did some research and indeed information on the topic seems vague and rare.
Some insightful comments can be found here:
Especially the remarks about the spawn() API. From what I've read, I guess "PJ" is just a flag for a given application program, being configured in an SBSD. If you use spawn() "the right way", the OS does not start a fresh job "from zero" but makes an already (pre-activated) PJ run.
It's not entirely clear to me
- how to properly send a PJ back to "PJ state" when work is done. Perhaps this is done automatically by the OS when exiting the main() function with return().
- If and how the OS (de|in)creases the PJ count to match the given workload. It's not clear if this automatic adjustment happens only when work enters through a communications entry in the SBSD.
Another source of some insight:
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.