You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To avoid a deadlock in the mirage tcpip-stack I have implemented an async version of the backend as a temporary workaround (enable with Basic_backend.create ~use_async_readers:true ()). When this is enabled, calls to the listen-function are wrapped in Lwt.async. This means that write never blocks and that potentially a large number of reader threads may be started if the writer is faster than the readers. It works for tcpip though, as it adjusts its rate.
The text was updated successfully, but these errors were encountered:
To avoid a deadlock in the mirage tcpip-stack I have implemented an async version of the backend as a temporary workaround (enable with
Basic_backend.create ~use_async_readers:true ()
). When this is enabled, calls to the listen-function are wrapped in Lwt.async. This means that write never blocks and that potentially a large number of reader threads may be started if the writer is faster than the readers. It works for tcpip though, as it adjusts its rate.The text was updated successfully, but these errors were encountered: