Lines Matching +full:output +full:- +full:only

9 …og messages at all with `CONFIG_LOG_BLOCK_IN_THREAD=y`, `CONFIG_LOG_BLOCK_IN_THREAD_TIMEOUT_MS=-1`.
15 > and should only be attempted in advanced use cases.
23 concerned with the ratio of the Output Rate to the Input Rate, and in that
24 case, the units themselves cancel-out. In the table we assume there exists an
27 | Name           | Input Rate | Output Rate | Rate |
28 |----------------|------------|-------------|------|
29 | Input-Limited  | 1          | N           | 1    |
31 | Output-Limited | 1          | 1/N         | 1/N  |
34 The resultant _Rate_ is always `Rate = MIN(Input Rate, Output Rate)`.
36 Rate-limiting of any kind can be described approximately as _back pressure_.
42 Many log backends, such as UARTs, have a built-in hardware FIFO that
43 inherently provides back-pressure; output log processing is rate-limited
46 rate-limited by the physical layer over which they operate, be it Gigabit
49 Even a trivial _message source_ or _message sink_ is still rate-limited by
54 ## Input-Limited Log Rate
56 The ideal scenario is when the output "bandwidth" exceeds the input rate. If
58 stall. We can also be sure that the output will be able to relieve
61 ## Rate-Matched Input and Output
63 When the input rate and output rates are equal, one might think this is the
66 cause the core log buffer to approach 100% capacity. Since the output log rate
67 is still only matched with the input log rate, the core log buffer capacity
71 operate in the _Input-limited Log Rate_ regime.
73 ## Output-Limited Log Rate
75 If the rate of output processing is less than the rate of input processing,
82 the output rate approaches 0 `[msg/s]`. If application or
87 Stalling a real-time application produces unexpected behaviour, so it is
88 advised to avoid this for any non-negligible amount of time.
96 Remediation could involve disabling the log backend and freeing any in-use