summaryrefslogtreecommitdiffstats
path: root/doc/developer/process-architecture.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/developer/process-architecture.rst')
-rw-r--r--doc/developer/process-architecture.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/developer/process-architecture.rst b/doc/developer/process-architecture.rst
index d2bf141a3..33ef278c4 100644
--- a/doc/developer/process-architecture.rst
+++ b/doc/developer/process-architecture.rst
@@ -47,7 +47,7 @@ section. For now it provides basic information necessary to understand the
interplay between the event system and kernel threads.
The core event system is implemented in :file:`lib/thread.[ch]`. The primary
-structure is ``struct event_master``, hereafter referred to as a
+structure is ``struct event_loop``, hereafter referred to as a
``threadmaster``. A ``threadmaster`` is a global state object, or context, that
holds all the tasks currently pending execution as well as statistics on tasks
that have already executed. The event system is driven by adding tasks to this
@@ -95,7 +95,7 @@ irrelevant for the time being) for the specific type. For example, to add a
::
- event_add_read(struct event_master *master, int (*handler)(struct event *), void *arg, int fd, struct event **ref);
+ event_add_read(struct event_loop *master, int (*handler)(struct event *), void *arg, int fd, struct event **ref);
The ``struct event`` is then created and added to the appropriate internal
datastructure within the ``threadmaster``. Note that the ``READ`` and