mirror of https://github.com/mkerrisk/man-pages
userfaultfd.2: Add note about asynchronous event delivery
Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
53004b3ba0
commit
20050169e1
|
@ -112,6 +112,18 @@ created for the child process,
|
|||
which allows userfaultfd monitor to perform user-space paging
|
||||
for the child process.
|
||||
|
||||
Unlike page faults which have to be synchronous and require
|
||||
explicit or implicit wakeup,
|
||||
all other events are delivered asynchronously and
|
||||
the non-cooperative process resumes execution as
|
||||
soon as manager executes
|
||||
.BR read(2).
|
||||
The userfaultfd manager should carefully synchronize calls
|
||||
to UFFDIO_COPY with the events processing.
|
||||
|
||||
The current asynchronous model of the event delivery is optimal for
|
||||
single threaded non-cooperative userfaultfd manager implementations.
|
||||
|
||||
.\" FIXME elaborate about non-cooperating mode, describe its limitations
|
||||
.\" for kernels before 4.11, features added in 4.11
|
||||
.\" and limitations remaining in 4.11
|
||||
|
|
Loading…
Reference in New Issue