Home
last modified time | relevance | path

Searched hist:1526 (Results 1 – 4 of 4) sorted by relevance

/unit/src/
H A Dnxt_port_memory.hdiff 1526:5c2a0b6f92e7 Sat Jul 25 08:06:00 UTC 2020 Max Romanov <max.romanov@nginx.com> Using plain shared memory for configuration pass.

There is no restrictions on configration size and using segmented shared memory
only doubles memory usage because to parse configration on router side,
it needs to be 'plain' e. g. located in single continous memory buffer.
H A Dnxt_port_memory.cdiff 1526:5c2a0b6f92e7 Sat Jul 25 08:06:00 UTC 2020 Max Romanov <max.romanov@nginx.com> Using plain shared memory for configuration pass.

There is no restrictions on configration size and using segmented shared memory
only doubles memory usage because to parse configration on router side,
it needs to be 'plain' e. g. located in single continous memory buffer.
H A Dnxt_controller.cdiff 1526:5c2a0b6f92e7 Sat Jul 25 08:06:00 UTC 2020 Max Romanov <max.romanov@nginx.com> Using plain shared memory for configuration pass.

There is no restrictions on configration size and using segmented shared memory
only doubles memory usage because to parse configration on router side,
it needs to be 'plain' e. g. located in single continous memory buffer.
H A Dnxt_router.cdiff 1526:5c2a0b6f92e7 Sat Jul 25 08:06:00 UTC 2020 Max Romanov <max.romanov@nginx.com> Using plain shared memory for configuration pass.

There is no restrictions on configration size and using segmented shared memory
only doubles memory usage because to parse configration on router side,
it needs to be 'plain' e. g. located in single continous memory buffer.