John Baldwin 9c20dc9963 Add more documentation regarding unsafe AIO requests.
The asynchronous I/O changes made previously result in different
behavior out of the box. Previously all AIO requests failed with
ENOSYS / SIGSYS unless aio.ko was explicitly loaded. Now, some AIO
requests complete and others ("unsafe" requests) fail with EOPNOTSUPP.

Reword the introductory paragraph in aio(4) to add a general
description of AIO before describing the vfs.aio.enable_unsafe sysctl.

Remove the ENOSYS error description from aio_fsync(2), aio_read(2),
and aio_write(2) and replace it with a description of EOPNOTSUPP.

Remove the ENOSYS error description from aio_mlock(2).

Log a message to the system log the first time a process requests an
"unsafe" AIO request that fails with EOPNOTSUPP. This is modeled on
the log message used for processes using the legacy pty devices.

Reviewed by:	kib (earlier version)
MFC after:	1 week
Sponsored by:	Chelsio Communications
Differential Revision:	https://reviews.freebsd.org/D7151
2016-07-21 22:49:47 +00:00
..
2015-06-13 19:20:56 +00:00
MFH
2016-04-04 23:55:32 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-02-10 04:20:39 +00:00
MFH
2016-03-02 16:14:46 +00:00
2016-05-12 03:53:20 +00:00
2016-06-14 16:55:05 +00:00
MFH
2016-03-02 16:14:46 +00:00
2016-02-16 02:14:30 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-03-02 16:14:46 +00:00
MFH
2016-04-04 23:55:32 +00:00
2016-06-04 14:57:25 +00:00
MFH
2016-03-14 18:54:29 +00:00
MFH
2016-04-11 15:24:59 +00:00
2016-05-18 15:25:45 +00:00
MFH
2016-04-13 16:19:50 +00:00
2016-05-29 01:43:28 +00:00
MFH
2016-04-16 02:32:12 +00:00
MFH
2016-04-04 23:55:32 +00:00