summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAngelos Evripiotis <jevripiotis@bloomberg.net>2019-06-05 14:10:45 +0100
committerbst-marge-bot <marge-bot@buildstream.build>2019-06-06 14:00:14 +0000
commitf40edee612a46ab28078f218d93ea3ea0d984e52 (patch)
treedf5f37f7c27049a2d62fca9e99c1280d578f923e /doc
parentcdbad2be1a4943cdf0159a19a4f256bad020170c (diff)
downloadbuildstream-f40edee612a46ab28078f218d93ea3ea0d984e52.tar.gz
Rename (spawn, fork) -> 'start process'
Avoid confusion by not referring to starting another process as 'spawning'. Note that 'spawn' is a process creation method, which is an alternative to forking. Say 'create child process' instead of 'fork' where it doesn't harm understanding. Although we currently only use the 'fork' method for creating subprocesses, there are reasons for us to support 'spawn' in the future. More information on forking and spawning: https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods
Diffstat (limited to 'doc')
-rw-r--r--doc/source/arch_scheduler.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/arch_scheduler.rst b/doc/source/arch_scheduler.rst
index 59efd68c2..4b0501495 100644
--- a/doc/source/arch_scheduler.rst
+++ b/doc/source/arch_scheduler.rst
@@ -8,13 +8,13 @@ dispatching *Jobs* to complete tasks on behalf of *Queues*.
Jobs
~~~~
-The basic functionality of spawning tasks is implemented by the base Job
+The basic functionality of multiprocessing tasks is implemented by the base Job
class, which is derived in a few ways but for now we'll only talk about the
ElementJob type since that is the most centric.
The Job class has the following responsibilities:
-* Spawning the given job as a subprocess.
+* Starting the given job as a subprocess.
* Offering an abstract method for subclasses to handle the outcome of
a job when it completes.