Willy Tarreau f793845f4a MEDIUM: clock: collect the monotonic time in clock_local_update_date() ... Now we collect this clock in clock_local_update_date(), the closest from the poller, which is also used when busy-polling, and the values is set into the thread's curr_mono_time which did not exist before. Later, clock_leaving_poll() just sets the prev_mono_time value from the curr_ one instead of retrieving the time at this specific point. It also means that the monotonic time will now also cover the time needed to update the global time, which should be negligible. Note that we don't collect the CPU time in the clock_local_update_date() function even though it's tempting, because when doing busy-polling, it would be collected on each round while being useless. Doing so will make sure that the local time always knows the monotonic time when it is available.		2024-09-17 09:08:10 +02:00
..
haproxy	MEDIUM: clock: collect the monotonic time in clock_local_update_date()	2024-09-17 09:08:10 +02:00
import	IMPORT: import cebtree (compact elastic binary trees)	2024-09-15 23:44:59 +02:00
make	BUILD: makefile: support USE_xxx=0 as well	2024-04-11 11:06:19 +02:00