Skip to content

Commit

Permalink
Clarify how sockets_size affects SHM segment size (#729)
Browse files Browse the repository at this point in the history
Signed-off-by: cferreiragonz <[email protected]>
  • Loading branch information
cferreiragonz authored Mar 18, 2024
1 parent 079dde6 commit 728dbea
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/fastdds/use_cases/tcp/tcp_large_data_with_options.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ All builtin transports can be configured by adjusting the following parameters:
Its maximum value is (2^32)-1 B for TCP and SHM and 65500 KB for UDP.
+ ``sockets_size``: Size of the send and receive socket buffers.
This value must be higher or equal than the ``max_msg_size`` to obtain a valid configuration.
It also defines the size of the shared memory segment, calculated as twice the value set.
Its maximum value is (2^32)-1 B.
+ ``non_blocking``: If set to true, the transport will use non-blocking sockets.
This can be useful to avoid blocking the application if the socket buffers are full.
Expand Down

0 comments on commit 728dbea

Please sign in to comment.