Default to a single receive thread on Windows
This works around a termination issue on Windows caused by the process sometimes being unable to send a packet to itself to wake up a thread stuck in a blocking read on a socket. Signed-off-by: Erik Boasson <eb@ilities.com>
This commit is contained in:
Erik Boasson
eboasson
parent
263d8016b8
commit
bb76798492
7 changed files with 75 additions and 34 deletions
|
|
@ -51,7 +51,7 @@ somewhat. It also causes the set of port numbers needed by Cyclone DDS to
|
|||
become predictable, which may be useful for firewall and NAT
|
||||
configuration.</p><p>The default value is: "single".</p>""" ] ]
|
||||
element ManySocketsMode {
|
||||
"false"|"true"|"single"|"none"|"many"
|
||||
("false"|"true"|"single"|"none"|"many")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>This element sets the level of standards conformance of this instance
|
||||
|
|
@ -78,7 +78,7 @@ though there is no good reason not to.</li></ul>
|
|||
<p>The default setting is "lax".</p><p>The default value is:
|
||||
"lax".</p>""" ] ]
|
||||
element StandardsConformance {
|
||||
"lax"|"strict"|"pedantic"
|
||||
("lax"|"strict"|"pedantic")
|
||||
}?
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
|
|
@ -444,13 +444,13 @@ is available.</p><p>The default value is: "false".</p>""" ] ]
|
|||
<p>This element allows selecting the transport to be used (udp, udp6,
|
||||
tcp, tcp6, raweth)</p><p>The default value is: "default".</p>""" ] ]
|
||||
element Transport {
|
||||
"default"|"udp"|"udp6"|"tcp"|"tcp6"|"raweth"
|
||||
("default"|"udp"|"udp6"|"tcp"|"tcp6"|"raweth")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>Deprecated (use Transport instead)</p><p>The default value is:
|
||||
"default".</p>""" ] ]
|
||||
element UseIPv6 {
|
||||
"false"|"true"|"default"
|
||||
("false"|"true"|"default")
|
||||
}?
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
|
|
@ -509,7 +509,7 @@ most efficient, and <i>full</i> is inefficient but certain to be
|
|||
compliant. See also Internal/ConservativeBuiltinReaderStartup.</p><p>The
|
||||
default value is: "writers".</p>""" ] ]
|
||||
element BuiltinEndpointSet {
|
||||
"full"|"writers"|"minimal"
|
||||
("full"|"writers"|"minimal")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>The ControlTopic element allows configured whether Cyclone DDS
|
||||
|
|
@ -735,10 +735,13 @@ is: "-1".</p>""" ] ]
|
|||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>This element controls whether all traffic is handled by a single
|
||||
receive thread or whether multiple receive threads may be used to improve
|
||||
latency. Currently multiple receive threads are only used for
|
||||
connectionless transport (e.g., UDP) and ManySocketsMode not set to
|
||||
single (the default).</p><p>The default value is: "true".</p>""" ] ]
|
||||
receive thread (false) or whether multiple receive threads may be used to
|
||||
improve latency (true). By default it is disabled on Windows because it
|
||||
appears that one cannot count on being able to send packets to oneself,
|
||||
which is necessary to stop the thread during shutdown. Currently multiple
|
||||
receive threads are only used for connectionless transport (e.g., UDP)
|
||||
and ManySocketsMode not set to single (the default).</p><p>The default
|
||||
value is: "default".</p>""" ] ]
|
||||
element MultipleReceiveThreads {
|
||||
[ a:documentation [ xml:lang="en" """
|
||||
<p>Receive threads dedicated to a single socket can only be triggered for
|
||||
|
|
@ -750,7 +753,7 @@ attribute before aborting.</p><p>The default value is:
|
|||
attribute maxretries {
|
||||
xsd:integer
|
||||
}?
|
||||
& xsd:boolean
|
||||
& ("false"|"true"|"default")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>This setting controls the delay between receipt of a HEARTBEAT
|
||||
|
|
@ -835,7 +838,7 @@ try to merge.</li></ul>
|
|||
Internal/RetransmitMergingPeriod.</p><p>The default value is:
|
||||
"never".</p>""" ] ]
|
||||
element RetransmitMerging {
|
||||
"never"|"adaptive"|"always"
|
||||
("never"|"adaptive"|"always")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>This setting determines the size of the time window in which a NACK of
|
||||
|
|
@ -1220,7 +1223,7 @@ using TCP.</p><p>The default value is: "false".</p>""" ] ]
|
|||
General/Transport instead.</p><p>The default value is:
|
||||
"default".</p>""" ] ]
|
||||
element Enable {
|
||||
"false"|"true"|"default"
|
||||
("false"|"true"|"default")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>This element enables the TCP_NODELAY socket option, preventing
|
||||
|
|
@ -1326,7 +1329,7 @@ from the underlying operating system to be able to assign some of the
|
|||
privileged scheduling classes.</p><p>The default value is:
|
||||
"default".</p>""" ] ]
|
||||
element Class {
|
||||
"realtime"|"timeshare"|"default"
|
||||
("realtime"|"timeshare"|"default")
|
||||
}?
|
||||
& [ a:documentation [ xml:lang="en" """
|
||||
<p>This element specifies the thread priority (decimal integer or
|
||||
|
|
@ -1467,7 +1470,7 @@ situation rather than the current situation. Currently, the most useful
|
|||
verbosity levels are <i>config</i>, <i>fine</i> and
|
||||
<i>finest</i>.</p><p>The default value is: "none".</p>""" ] ]
|
||||
element Verbosity {
|
||||
"finest"|"finer"|"fine"|"config"|"info"|"warning"|"severe"|"none"
|
||||
("finest"|"finer"|"fine"|"config"|"info"|"warning"|"severe"|"none")
|
||||
}?
|
||||
}?
|
||||
}?
|
||||
|
|
|
|||
|
|
@ -1013,14 +1013,24 @@ is: &quot;-1&quot;.</p></xs:documentation>
|
|||
<xs:annotation>
|
||||
<xs:documentation>
|
||||
<p>This element controls whether all traffic is handled by a single
|
||||
receive thread or whether multiple receive threads may be used to improve
|
||||
latency. Currently multiple receive threads are only used for
|
||||
connectionless transport (e.g., UDP) and ManySocketsMode not set to
|
||||
single (the default).</p><p>The default value is: &quot;true&quot;.</p></xs:documentation>
|
||||
receive thread (false) or whether multiple receive threads may be used to
|
||||
improve latency (true). By default it is disabled on Windows because it
|
||||
appears that one cannot count on being able to send packets to oneself,
|
||||
which is necessary to stop the thread during shutdown. Currently multiple
|
||||
receive threads are only used for connectionless transport (e.g., UDP)
|
||||
and ManySocketsMode not set to single (the default).</p><p>The default
|
||||
value is: &quot;default&quot;.</p></xs:documentation>
|
||||
</xs:annotation>
|
||||
<xs:complexType>
|
||||
<xs:simpleContent>
|
||||
<xs:extension base="xs:boolean">
|
||||
<xs:restriction base="xs:anyType">
|
||||
<xs:simpleType>
|
||||
<xs:restriction base="xs:token">
|
||||
<xs:enumeration value="false"/>
|
||||
<xs:enumeration value="true"/>
|
||||
<xs:enumeration value="default"/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
<xs:attribute name="maxretries" type="xs:integer">
|
||||
<xs:annotation>
|
||||
<xs:documentation>
|
||||
|
|
@ -1032,7 +1042,7 @@ attribute before aborting.</p><p>The default value is:
|
|||
&quot;4294967295&quot;.</p></xs:documentation>
|
||||
</xs:annotation>
|
||||
</xs:attribute>
|
||||
</xs:extension>
|
||||
</xs:restriction>
|
||||
</xs:simpleContent>
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue