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
The current behavior on Windows is to only support asynchronous callbacks for ring buffer maps. The callback will be automatically invoked when data is available.
On linux there are no asynchronous callbacks for ringbuffers and the callback is only called inside calls to ring_buffer__poll() and ring_buffer__consume().
This will be a major breaking change to the ring buffer behavior, so should be put off until other API breaking changes are made. This also depends on #3848 being completed to support synchronous consumers.
OS information
No response
Steps taken to reproduce bug
Call ring_buffer__new.
Write events into ring buffer
callback will be automatically invoked after records are written.
Expected behavior
Expected behaviour on linux is that callback is not called outside of ring buffer poll and consume. This should eventually become the Windows default to resolve this incompatibility.
Actual outcome
On Windows there are only asynchronous callbacks right now, so the callback could be invoked as soon as it is attached.
Additional details
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
The current behavior on Windows is to only support asynchronous callbacks for ring buffer maps. The callback will be automatically invoked when data is available.
On linux there are no asynchronous callbacks for ringbuffers and the callback is only called inside calls to
ring_buffer__poll()
andring_buffer__consume()
.This will be a major breaking change to the ring buffer behavior, so should be put off until other API breaking changes are made. This also depends on #3848 being completed to support synchronous consumers.
OS information
No response
Steps taken to reproduce bug
ring_buffer__new
.Expected behavior
Expected behaviour on linux is that callback is not called outside of ring buffer poll and consume. This should eventually become the Windows default to resolve this incompatibility.
Actual outcome
On Windows there are only asynchronous callbacks right now, so the callback could be invoked as soon as it is attached.
Additional details
No response
The text was updated successfully, but these errors were encountered: