work queues in event engine
Igor Sysoev
igor at sysoev.ru
Mon Oct 2 10:35:33 UTC 2017
On 30 Sep 2017, at 11:38, 734819342 at qq.com wrote:
> Hello:
>
> Why there are many work queues in event engine? And what for respectively?
>
>
> nxt_work_queue_cache_t work_queue_cache;
> nxt_work_queue_t *current_work_queue;
> nxt_work_queue_t fast_work_queue;
> nxt_work_queue_t accept_work_queue;
> nxt_work_queue_t read_work_queue;
> nxt_work_queue_t socket_work_queue;
> nxt_work_queue_t connect_work_queue;
> nxt_work_queue_t write_work_queue;
> nxt_work_queue_t shutdown_work_queue;
> nxt_work_queue_t close_work_queue;
>
> nxt_locked_work_queue_t locked_work_queue;
Syscall related operations are batched in queues.
It is unfinished now but will be completed soon.
--
Igor Sysoev
http://nginx.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/unit/attachments/20171002/cf85654f/attachment.html>
More information about the unit
mailing list