Willy Tarreau 501260bf67 MEDIUM: task: always ensure that the run queue is consistent ... As found by Thierry Fournier, if a task manages to kill another one and if this other task is the next one in the run queue, we can do whatever including crashing, because the scheduler restarts from the saved next task. For now, there is no such concept of a task killing another one, but with Lua it will come. A solution consists in always performing the lookup of the first task in the scheduler's loop, but it's expensive and costs around 2% of the performance. Another solution consists in keeping a global next run queue node and ensuring that when this task gets removed, it updates this pointer to the next one. This allows to simplify the code a bit and in the end to slightly increase the performance (0.3-0.5%). The mechanism might still be usable if we later migrate to a multi-threaded scheduler.		2015-02-23 16:07:01 +01:00
..
common	MEDIUM: regex: add support for passing regex flags to regex_exec_match()	2015-01-22 14:24:53 +01:00
import
proto	MEDIUM: task: always ensure that the run queue is consistent	2015-02-23 16:07:01 +01:00
types	MINOR: ssl/server: add the "no-ssl-reuse" server option	2015-02-06 18:04:08 +01:00