Emeric Brun c60def8368 MAJOR: threads/task: handle multithread on task scheduler ... 2 global locks have been added to protect, respectively, the run queue and the wait queue. And a process mask has been added on each task. Like for FDs, this mask is used to know which threads are allowed to process a task. For many tasks, all threads are granted. And this must be your first intension when you create a new task, else you have a good reason to make a task sticky on some threads. This is then the responsibility to the process callback to lock what have to be locked in the task context. Nevertheless, all tasks linked to a session must be sticky on the thread creating the session. It is important that I/O handlers processing session FDs and these tasks run on the same thread to avoid conflicts.		2017-10-31 13:58:30 +01:00
..
common	MAJOR: threads/task: handle multithread on task scheduler	2017-10-31 13:58:30 +01:00
import	MINOR: threads: Add atomic-ops and plock includes in import dir	2017-10-31 11:36:13 +01:00
proto	MAJOR: threads/task: handle multithread on task scheduler	2017-10-31 13:58:30 +01:00
types	MAJOR: threads/task: handle multithread on task scheduler	2017-10-31 13:58:30 +01:00