haproxy/dev/haring
Willy Tarreau cbbee15462 CLEANUP: ring: rename the ring lock "RING_LOCK" instead of "LOGSRV_LOCK"
The ring lock was initially mostly used for the logs and used to inherit
its name in lock stats. Now that it's exclusively used by rings, let's
rename it accordingly.
2023-09-20 21:38:33 +02:00
..
README DEV: haring: update readme to suggest using the same build options for haring 2023-05-04 08:13:44 +02:00
haring.c CLEANUP: ring: rename the ring lock "RING_LOCK" instead of "LOGSRV_LOCK" 2023-09-20 21:38:33 +02:00

README

This needs to be built from the top makefile, for example :

  make dev/haring/haring

If HAProxy is built with special options such -DDEBUG_THREAD or with
multi-threading support enabled (which changes the ring's header size),
it can be worth reusing the same build options for haring, usually they
will remain compatible, and will simplify the handling of different file
layouts, at the expense of dragging more dependencies into the executable.