src/lib/libc/sys/aio_fsync.2, branch releng/14.0 FreeBSD source tree Remove $FreeBSD$: two-line nroff pattern 2023-08-16T17:55:10+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:55:10+00:00 fa9896e082a1046ff4fbc75fcba4d18d1f2efc19 Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/ 
Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/
aio_fsync(2): Support O_DSYNC. 2021-01-08T00:15:56+00:00 Thomas Munro tmunro@FreeBSD.org 2021-01-07T11:11:38+00:00 801ac943ea0821bbb34c69688a7e7bb126d8cf8d aio_fsync(O_DSYNC, ...) is the asynchronous version of fdatasync(2). Reviewed by: kib, asomers, jhb Differential Review: https://reviews.freebsd.org/D25071 
aio_fsync(O_DSYNC, ...) is the asynchronous version of fdatasync(2).

Reviewed by: kib, asomers, jhb
Differential Review: https://reviews.freebsd.org/D25071
Fix various nits in the aio operation manpages. 2016-08-19T17:37:32+00:00 John Baldwin jhb@FreeBSD.org 2016-08-19T17:37:32+00:00 4092a25cd0c0e9de2912f69a1e1d1b8ff0224000 - Avoid double use of "request" in a single sentence. Instead, describe aio_sigevent as being used to request notification of the associated operation's completion. This matches the language used to describe aio_sigevent in aio(4). - Simplify the prohibition on modifying buffers while requests are in flight. - Fix case mismatch. - Drop note about not using stack variables. C programmers should be able to figure out if a stack variable is safe based on the later warning about the life cycle requirements of control blocks. - Remove prohibition on modifying the I/O buffer for aio_fsync() since it does not use an I/O buffer. For aio_mlock(), prohibit modifications to the mapping (e.g. due to mprotect, munmap, mmap, etc.) but do not prohibit modifications to the memory backing the buffer (stores into the pages backing the buffer). Requested by: wblock (1,2), kib (4) Reviewed by: kib, rpokala, wblock MFC after: 3 days Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D7462 
- Avoid double use of "request" in a single sentence.  Instead, describe
  aio_sigevent as being used to request notification of the associated
  operation's completion.  This matches the language used to describe
  aio_sigevent in aio(4).
- Simplify the prohibition on modifying buffers while requests are in
  flight.
- Fix case mismatch.
- Drop note about not using stack variables. C programmers should be able
  to figure out if a stack variable is safe based on the later warning
  about the life cycle requirements of control blocks.
- Remove prohibition on modifying the I/O buffer for aio_fsync() since
  it does not use an I/O buffer.  For aio_mlock(), prohibit modifications
  to the mapping (e.g. due to mprotect, munmap, mmap, etc.) but do not
  prohibit modifications to the memory backing the buffer (stores into
  the pages backing the buffer).

Requested by:	wblock (1,2), kib (4)
Reviewed by:	kib, rpokala, wblock
MFC after:	3 days
Sponsored by:	Chelsio Communications
Differential Revision:	https://reviews.freebsd.org/D7462
Add more documentation regarding unsafe AIO requests. 2016-07-21T22:49:47+00:00 John Baldwin jhb@FreeBSD.org 2016-07-21T22:49:47+00:00 9c20dc9963aa998fbb18991f2048e9c4eaa8f98d 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 
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
Add documentation for the sigevent structure. 2016-07-15T15:12:56+00:00 John Baldwin jhb@FreeBSD.org 2016-07-15T15:12:56+00:00 463970da7b4ccd44981e325dac9b24c12ccd3da6 - Add a sigevent(3) manpage to give a general overview of the sigevent structure and the available notification mechanisms. - Document that AIO requests contain a nested sigevent structure that can be used to request completion notification. - Expand the sigevent details in other manuals to note details such as the extra values stored in a queued signal's information or in a posted kevent. Reviewed by: kib MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D7122 
- Add a sigevent(3) manpage to give a general overview of the sigevent
  structure and the available notification mechanisms.
- Document that AIO requests contain a nested sigevent structure that can
  be used to request completion notification.
- Expand the sigevent details in other manuals to note details such as
  the extra values stored in a queued signal's information or in a posted
  kevent.

Reviewed by:	kib
MFC after:	3 days
Differential Revision:	https://reviews.freebsd.org/D7122
- Fix EBADF description, in following the future POSIX tc and what FreeBSD 2013-12-27T16:57:38+00:00 Sergey Kandaurov pluknet@FreeBSD.org 2013-12-27T16:57:38+00:00 d3178d7d2775aa1027499772bfdbaa134429e75a actually implements. - Improve grammar: use more preferred "can", not "could". Submitted by: jilles 
  actually implements.
- Improve grammar: use more preferred "can", not "could".

Submitted by:	jilles
Provide the manual page for aio_fsync(2). 2013-12-26T19:16:30+00:00 Sergey Kandaurov pluknet@FreeBSD.org 2013-12-26T19:16:30+00:00 e44aa9fde0a36f3a24b2ee5771ef0eea94d6e71f Reviewed by: davidxu MFC after: 1 week 
Reviewed by:	davidxu
MFC after:	1 week