From 8dc68f3c751b96183a5009f9ef001842d7a2c4e6 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Tue, 19 Nov 2024 16:26:04 +0100 Subject: [PATCH] DOC: sched: document the missing TASK_F_UEVT* flags These are user-defined one-shot events that are application-specific and reset upon wakeup and were not documented. No backport is needed since these were added to 3.1. --- doc/internals/api/scheduler.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/internals/api/scheduler.txt b/doc/internals/api/scheduler.txt index 70230d163..0b4459817 100644 --- a/doc/internals/api/scheduler.txt +++ b/doc/internals/api/scheduler.txt @@ -208,6 +208,11 @@ state field before the call to ->process() - TASK_WOKEN_OTHER any other application-defined wake-up reason. + - TASK_F_UEVT1 one-shot user-defined event type 1. This is application + specific, and reset to 0 when the handler is called. + + - TASK_F_UEVT2 one-shot user-defined event type 2. This is application + specific, and reset to 0 when the handler is called. In addition, a few persistent flags may be observed or manipulated by the application, both for tasks and tasklets: