Home
last modified time | relevance | path

Searched hist:122 (Results 1 – 9 of 9) sorted by relevance

/unit/src/
H A Dnxt_buf_pool.cdiff 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 Dnxt_buf.cdiff 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 Dnxt_log.hdiff 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 Dnxt_buf.hdiff 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 Dnxt_port_memory.cdiff 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 Dnxt_port_socket.cdiff 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 Dnxt_port.cdiff 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 Dnxt_port.hdiff 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 Dnxt_router.cdiff 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.