Lines Matching full:manager

43 passed using unix domain sockets to a manager process, so the same
44 manager process could handle the userfaults of a multitude of
47 themselves on the same region the manager is already tracking, which
366 When the ``userfaultfd`` is monitored by an external manager, the manager
368 layout. Userfaultfd can notify the manager about such changes using
370 manager has to explicitly enable these events by setting appropriate
376 	duplicated into the newly created process. The manager
383 	different location, the manager will receive
394 	enable notifications about memory unmapping. The manager will
400 ``userfaultfd`` manager. In the former case, the virtual memory is
403 delivered to the manager. The proper resolution for such page fault is
407 ``userfaultfd`` context for such area disappears too and the manager will
409 notification is required in order to prevent manager from using
415 soon as manager executes read(). The ``userfaultfd`` manager should
424 single threaded non-cooperative ``userfaultfd`` manager implementations. A
427 non cooperative manager, for example to allow ``UFFDIO_COPY`` ioctls to