Lines Matching full:space

14   the given monitoring target address-space and available set of
19   interfaces for the user space, on top of the core layer.
27 the given target address space.  On the other hand, the accuracy and overhead
29 space.  DAMON separates the two parts in different layers, namely DAMON
34 Due to this design, users can extend DAMON for any address space by configuring
38 For example, physical memory, virtual memory, swap space, those for specific
48 programming interface to all kernel space components such as subsystems and
51 used by the user space end users.
59 1. Identification of the monitoring target address range for the address space.
60 2. Access check of specific address range in the target space.
69 This is only for the virtual address space monitoring operations
70 implementation.  That for the physical address space simply asks users to
73 Only small parts in the super-huge virtual address space of the processes are
82 distinct regions that cover every mapped area of the address space.  The two
84 address space.  The two biggest unmapped areas would be the gap between the
207 Dynamic Target Space Updates Handling
272 normally depends on the monitoring target address space.  For example, the code
406 The programming interface for kernel space data access-aware applications.
419 provide any direct interface for the user space.  Such interfaces should be
424 user space.  The user space can build their efficient data access-aware
431 DAMON modules that provide user space ABIs for general purpose DAMON usage in
436 user-space.  Please note that DAMON debugfs interface is currently deprecated.
442 API, and return the results to the user-space.
444 The ABIs are designed to be used for user space applications development,
446 user space tools.  One such Python-written user space tool is available at
458 DAMON modules that provide user space ABI for specific purpose DAMON usage.
469 simple and optimized user space interfaces are available.  Currently, two