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
..
2016-06-04 20:20:14 +00:00
2014-06-26 10:21:00 +00:00
2013-01-15 14:09:08 +00:00
2016-02-04 18:03:06 +00:00
2015-10-20 23:52:37 +00:00
2013-08-16 13:16:27 +00:00
2011-11-10 06:20:18 +00:00
2016-03-09 13:45:03 +00:00
2016-02-29 17:20:04 +00:00
2015-03-29 19:14:41 +00:00
2016-05-03 15:58:35 +00:00
2016-02-18 18:50:03 +00:00
2014-05-30 02:16:28 +00:00
2016-03-18 08:47:17 +00:00
2012-05-08 18:56:21 +00:00
2015-07-07 19:23:59 +00:00
2012-05-08 18:56:21 +00:00
2015-04-26 10:52:37 +00:00
2015-08-21 02:42:14 +00:00
2016-02-29 17:22:34 +00:00
2015-02-07 13:11:45 +00:00
2014-06-24 20:23:18 +00:00
2012-05-08 18:56:21 +00:00
2016-01-18 20:21:38 +00:00