Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update OS_TimedRead and OS_TimedWrite to support sub-millisecond timeout resolution #1455

Closed
dmknutsen opened this issue Mar 6, 2024 · 0 comments · Fixed by #1456
Closed
Assignees

Comments

@dmknutsen
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We are supporting a user that requires higher timeout fidelity than what is currently supported.

Describe the solution you'd like
Sub-millisecond timeout resolution.

Requester Info
Dan Knutsen
NASA Goddard

@jphickey jphickey self-assigned this Mar 6, 2024
jphickey added a commit to jphickey/osal that referenced this issue Mar 6, 2024
Implement high-res timed operations for streams.  This uses an absolute
time via the OS_time_t value, which has a default resolution of 0.1usec
but is configurable.
jphickey added a commit to jphickey/osal that referenced this issue May 20, 2024
Add API calls equivalent to existing calls that use an absolute timeout
as opposed to a relative timeout.  The absolute timeout can support
resolution of 0.1 usec in the default configuration.

Internally this primarily affects the underlying call to select().

Note that per the definition of select() in POSIX, it uses a
"struct timeval" which has a resolution of 1 usec.
jphickey added a commit to jphickey/osal that referenced this issue May 20, 2024
Add API calls equivalent to existing calls that use an absolute timeout
as opposed to a relative timeout.  The absolute timeout can support
resolution of 0.1 usec in the default configuration.

Internally this primarily affects the underlying call to select().

Note that per the definition of select() in POSIX, it uses a
"struct timeval" which has a resolution of 1 usec.
jphickey added a commit to jphickey/osal that referenced this issue May 20, 2024
Add API calls equivalent to existing calls that use an absolute timeout
as opposed to a relative timeout.  The absolute timeout can support
resolution of 0.1 usec in the default configuration.

Internally this primarily affects the underlying call to select().

Note that per the definition of select() in POSIX, it uses a
"struct timeval" which has a resolution of 1 usec.
dzbaker added a commit that referenced this issue Jul 2, 2024
dzbaker added a commit that referenced this issue Jul 2, 2024
@dzbaker dzbaker closed this as completed in ec30aa7 Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants