diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2022-12-11 17:20:40 +0100 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2023-03-24 13:32:17 +0100 |
| commit | 2453d15dbf7fff2d897c2182886486732be8ac35 (patch) | |
| tree | 7a054859acf25689f67d5df7aa9d50b20bca4b62 /doc | |
| parent | *: Convert a bunch of thread_XX to event_XX (diff) | |
| download | frr-2453d15dbf7fff2d897c2182886486732be8ac35.tar.xz frr-2453d15dbf7fff2d897c2182886486732be8ac35.zip | |
*: Convert struct thread_master to struct event_master and it's ilk
Convert the `struct thread_master` to `struct event_master`
across the code base.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/developer/modules.rst | 2 | ||||
| -rw-r--r-- | doc/developer/process-architecture.rst | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/developer/modules.rst b/doc/developer/modules.rst index 89d2f81f1..6dd65d67d 100644 --- a/doc/developer/modules.rst +++ b/doc/developer/modules.rst @@ -58,7 +58,7 @@ Basic boilerplate: #include "libfrr.h" #include "event.h" - static int module_late_init(struct thread_master *master) + static int module_late_init(struct event_master *master) { /* Do initialization stuff here */ return 0; diff --git a/doc/developer/process-architecture.rst b/doc/developer/process-architecture.rst index 181baecea..d2bf141a3 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 thread_master``, hereafter referred to as a +structure is ``struct event_master``, 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 thread_master *master, int (*handler)(struct event *), void *arg, int fd, struct event **ref); + event_add_read(struct event_master *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 |