audio.4: O_NONBLOCK isn't the actual problem

This commit is contained in:
nia 2020-03-16 09:20:01 +00:00
parent b65a7a635c
commit bfc83a571c
1 changed files with 6 additions and 4 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: audio.4,v 1.96 2020/03/16 08:50:06 nia Exp $
.\" $NetBSD: audio.4,v 1.97 2020/03/16 09:20:01 nia Exp $
.\"
.\" Copyright (c) 1996 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -818,6 +818,8 @@ If the device is used in
.Xr mmap 2
it is currently always mapped for writing (playing) due to VM system weirdness.
.Sh CAVEATS
The audio device cannot be reliably used with O_NONBLOCK or event notification
mechanisms. Users are generally expected to only read and write a limited number
of samples at a time, limiting the time spent in the system call.
The audio device cannot be reliably used with event notification mechanisms
such as
.Xr poll 2 .
Most users are expected to only read and write a limited number of samples at
a time, limiting the time spent in the system call.