eb3d5f464d
We're now locking the tail while looking for some room in the ring. In fact it's still while writing to it, but the goal definitely is to get rid of the lock ASAP. For this we reserve the topmost bit of the tail as a lock, which may have as a possible visible effect that buffers will be limited to 2GB instead of 4GB on 32-bit machines (though in practise, good luck for allocating more than 2GB contiguous on 32-bit), but in practice since the size is read with atol() and some operating systems limit it to LONG_MAX unless passing negative numbers, the limit is already there. For now the impact on x86_64 is significant (drop from 2.35 to 1.4M/s on 48 threads on EPYC 24 cores) but this situation is only temporary so that changes can be reviewable and bisectable. Other approaches were attempted, such as using XCHG instead, which is slightly faster on x86 with low thread counts (but causes more write contention), and forces readers to stall under heavy traffic because they can't access a valid value for the queue anymore. A CAS requires preloading the value and is les good on ARMv8.1. XADD could also be considered with 12-13 upper bits of the offset dedicated to locking, but that looks overkill. |
||
|---|---|---|
| .. | ||
| README | ||
| haring.c | ||
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.