Searched hist:122 (Results 1 – 9 of 9) sorted by relevance
/unit/src/ |
H A D | nxt_buf_pool.c | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_buf.c | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_log.h | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_buf.h | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_port_memory.c | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_port_socket.c | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_port.c | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_port.h | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|
H A D | nxt_router.c | diff 122:d18727e877c6 Fri Jul 07 13:01:00 UTC 2017 Max Romanov <max.romanov@nginx.com> Redirecting buffer completion handler to specific engine.
There is a case in router where we use port in router connection thread. Buffers are allocated within connection memory pool which can be used only in this router thread. sendmsg() can be postponed into main router thread and completion handler will compare current engine and post itself to correct engine.
|