mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-29 14:01:50 +01:00
8cdc167df8
Tasklets may be woken up to run on the calling thread or by a specific thread (the owner). But since we use a non-thread safe mechanism when the calling thread is also the for the owner, there may sometimes be collisions when two threads decide to wake the same tasklet up at the same time and one of them is the owner. This is more of a matter of usage than code, in that a tasklet usually is designed to be woken up and executed on the calling thread only (most cases) or on a specific thread. Thus it is a property of the tasklet itself as this solely depends how the code is constructed around it. This patch performs a small change to address this. By default tasklet_new() creates a "local" tasklet, which will run on the calling thread, like in 2.0. This is done by setting tl->tid to a negative value. If the caller wants the tasklet to run exclusively on a specific thread, it just has to set tl->tid, which is already what shared tasklet callers do anyway. No backport is needed.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)