From 9e4895da833b7777e69efc173f5dc777aaea3201 Mon Sep 17 00:00:00 2001
From: Rickard Green This field is used to pass driver capability information to the
- runtime system. If the This field is used to pass driver capability and other
+ information to the runtime system. If the
+
Sets and gets limits that will be used for controling the + busy state of the port message queue.
+The port message queue will be set into a busy
+ state when the amount of command data queued on the
+ message queue reaches the
Valid limits are values in the range
+
By passing a pointer to an integer variable containing
+ the value
The busy message queue feature can be disabled either
+ by setting the
Processes sending command data to the port will be suspended + if either the port is busy or if the port message queue is + busy. Suspended processes will be resumed when neither the + port is busy, nor the port message queue is busy.
+ +For information about busy port functionality
+ see the documentation of the
+
This function set and resets the busy status of the port. If
-
When the port is busy, sending to it with
This function set and unset the busy state of the port. If
+
Processes sending command data to the port will be suspended
+ if either the port is busy or if the port message queue
+ is busy. Suspended processes will be resumed when neither the
+ port is busy, nor the port message queue is busy. Command data
+ is in this context data passed to the port using either
+
If the
For information about busy port message queue functionality
+ see the documentation of the
+
The socket message queue will be set into a busy + state when the amount of data queued on the message + queue reaches this limit. Note that this limit only + concerns data that have not yet reached the ERTS internal + socket implementation. Default value used is 8 kB.
+Senders of data to the socket will be suspended if + either the socket message queue is busy, or the socket + itself is busy.
+For more information see the
Note that distribution sockets will disable the use of
+
The socket will be set into a busy state when the amount + of data queued internally by the ERTS socket implementation + reaches this limit. Default value used is 8 kB.
+Senders of data to the socket will be suspended if + either the socket message queue is busy, or the socket + itself is busy.
+For more information see the
Enables/disables periodic transmission on a connected @@ -495,6 +525,40 @@ fe80::204:acff:fe17:bf38 considered broken and an error message will be sent to the controlling process. Default disabled.
If the socket message queue is in a busy state, the + socket message queue will be set in a not busy state when + the amount of data queued in the message queue falls + below this limit. Note that this limit only concerns data + that have not yet reached the ERTS internal socket + implementation. Default value used is 4 kB.
+Senders that have been suspended due to either a + busy message queue or a busy socket, will be resumed + when neither the socket message queue, nor the socket + are busy.
+For more information see the
Note that distribution sockets will disable the use of
+
If the socket is in a busy state, the socket will + be set in a not busy state when the amount of data + queued internally by the ERTS socket implementation + falls below this limit. Default value used is 4 kB.
+Senders that have been suspended due to either a + busy message queue or a busy socket, will be resumed + when neither the socket message queue, nor the socket + are busy.
+For more information see the
If