DDS_SystemResourceLimitsQosPolicy Struct Reference

<<cert>> Resource limits that apply only to DDS_DomainParticipantFactory More...

#include <dds_c_infrastructure.h>

Data Fields
DDS_Long	max_participants
	The maximum number of DomainParticipants (DDS_DomainParticipant) the DDS_DomainParticipantFactory can manage.
DDS_Long	max_components
	The maximum number of components that may be registered on the DDS_DomainParticipantFactory. Note that changing this value can cause a DDS_DomainParticipantFactory to free and reallocate memory.

Detailed Description

<<cert>> Resource limits that apply only to DDS_DomainParticipantFactory

This QoS policy is an extension to the DDS standard.

Entity:

DDS_DomainParticipantFactory

Properties:

RxO = N/A
Changeable = NO

Field Documentation

max_participants

DDS_Long DDS_SystemResourceLimitsQosPolicy::max_participants

The maximum number of DomainParticipants (DDS_DomainParticipant) the DDS_DomainParticipantFactory can manage.

The DDS_DomainParticipantFactory can manage up to the number of DomainParticipants specified by this limit. However, the actual number of DomainParticipants that can be created with DDS_DomainParticipantFactory_create_participant is further limited by the following constraints:

• Available memory and system resources such as network sockets and shared memory resources.

• The maximum number of OSAPI_SystemProperty::max_timers available. Each DDS_DomainParticipant requires one timer plus one timer if Zero Copy v2 is enabled as a transport in DDS_TransportQosPolicy::enabled_transports.

• The maximum number of OSAPI_SystemProperty::max_user_blocking_threads. Each receive-thread requires one blocking resource.

• DDS uses the DDS_WireProtocolQosPolicy::rtps_well_known_ports to discover other participants. The number of DomainParticipants that can be created is limited by port aliasing where ports calculated for different DDS domain IDs may overlap. RTI Connext DDS Micro does not determine if port aliasing may occur and the application must ensure that port aliasing does not occur.

Note that this value can only be modified until the first DDS_DomainParticipant is created and may cause memory reallocation.

[default] 1

[range] [1, INT_MAX] with default QoS settings. Additional DDS_DomainParticipant objects can be allocated by changing the DDS_WireProtocolQosPolicy::rtps_well_known_ports QoS policy on all DDS_DomainParticipant's on a node.

max_components

DDS_Long DDS_SystemResourceLimitsQosPolicy::max_components

The maximum number of components that may be registered on the DDS_DomainParticipantFactory. Note that changing this value can cause a DDS_DomainParticipantFactory to free and reallocate memory.

RTI Connext DDS Micro consists of a number of plugins and components that perform various tasks. For example, the UDP transport and the DPDE discovery plugins are RTI Connext DDS Micro components. This resource-limit limits the number of components that can be registered with RTI Connext DDS Micro. This value should only be changed if plugins and components are developed.

[default] 16

[range] [1, INT_MAX]