| /linux/Documentation/mm/damon/ |
| H A D | index.rst | 4 DAMON: Data Access MONitoring and Access-aware System Operations
19 access-aware fashion. Because the features are also exposed to the :doc:`user
27 spaces </admin-guide/mm/damon/index>` can do access-aware system operations
|
| H A D | design.rst | 32 overhead/accuracy control and access-aware system operations on top of the
393 One common purpose of data access monitoring is access-aware system efficiency
752 The programming interface for kernel space data access-aware applications.
755 access-aware applications using DAMON's core features. For this, DAMON exposes
770 for general purpose DAMON control and special purpose data access-aware system
772 user space. The user space can build their efficient data access-aware
800 Special-Purpose Access-aware Kernel Modules
806 runtime. For each special-purpose system-wide data access-aware system
|
| /linux/Documentation/driver-api/usb/ |
| H A D | dma.rst | 14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
|
| /linux/tools/testing/selftests/kvm/arm64/ |
| H A D | debug-exceptions.c | 183 /* Setup a context-aware breakpoint for Linked Context ID Match */ in install_wp_ctx()
189 /* Setup a linked watchpoint (linked to the context-aware breakpoint) */ in install_wp_ctx()
204 /* Setup a context-aware breakpoint for Linked Context ID Match */ in install_hw_bp_ctx()
212 * to the context-aware breakpoint. in install_hw_bp_ctx()
534 * context-aware breakpoint# with the given ID_AA64DFR0_EL1 configuration.
548 /* Number of context aware breakpoints */ in test_guest_debug_exceptions_all()
554 /* Number of normal (non-context aware) breakpoints */ in test_guest_debug_exceptions_all()
557 /* Lowest context aware breakpoint number */ in test_guest_debug_exceptions_all()
|
| /linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | vxlan.sh | 116 log_test "vxlan device with a vlan-aware bridge"
873 log_test "vlan-aware - enslavement to vlan-aware bridge"
882 log_test "vlan-aware - two vnis mapped to the same vlan"
896 log_test "vlan-aware - failed enslavement to vlan-aware bridge"
902 # (i.e., different TTL) are enslaved to the same VLAN-aware bridge,
917 log_test "vlan-aware - failed enslavement to bridge due to conflict"
929 # Create a simple setup with two VxLAN devices and a single VLAN-aware
974 log_info "vxlan entry offload indication - vlan-aware"
1172 log_info "offload indication - replay & cleanup - vlan aware"
|
| H A D | extack.sh | 125 # Test with VLAN-aware bridge.
163 # Only one VLAN-aware bridge is supported, so this should fail with
169 log_test "extack - multiple VLAN-aware bridges creation"
|
| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 2 Capacity Aware Scheduling
133 Capacity aware scheduling requires an expression of a task's requirements with
248 This means that while the capacity aware scheduling criteria will be written
252 3. Capacity aware scheduling requirements
269 As stated in 2.2, capacity-aware scheduling requires a frequency-invariant task
277 when the kernel is aware of the switched-to frequency (also employed by
331 5. Capacity aware scheduling implementation
370 Wakeup CPU selection in CFS can be eclipsed by Energy Aware Scheduling
|
| /linux/samples/damon/ |
| H A D | Kconfig | 18 bool "DAMON sample module for access-aware proactive reclamation"
21 This builds DAMON sample module for access-aware proactive
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | shrinker_debugfs.rst | 59 If the shrinker is not memcg-aware or CONFIG_MEMCG is off, 0 is printed
60 as cgroup inode id. If the shrinker is not numa-aware, 0's are printed
112 For a non-memcg-aware shrinker or on a system with no memory
|
| /linux/include/linux/ |
| H A D | shrinker.h | 13 * Bitmap and deferred work of shrinker::id corresponding to memcg-aware
37 /* current node being shrunk (for NUMA aware shrinkers) */
54 /* current memcg being shrunk (for memcg aware shrinkers) */
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | st,stm32mp25-rifsc.yaml | 20 for peripherals), assign all non-RIF aware peripherals to zero, one or
23 unit), assign all non RIF-aware bus master to one security domain by
|
| /linux/Documentation/gpu/ |
| H A D | drm-compute.rst | 42 eviction would be made cgroup aware. This allows the GPU to be partitioned
48 be made cgroup aware.
|
| /linux/arch/arm/mach-sa1100/include/mach/ |
| H A D | irqs.h | 86 * Neponset, SA1111 and UCB1x00 are sparse IRQ aware, so can dynamically
89 * LoCoMo has 4 additional IRQs, but is not sparse IRQ aware, and so has
|
| /linux/include/asm-generic/ |
| H A D | rwonce.h | 5 * READ_ONCE and WRITE_ONCE, but only when the compiler is aware of some
6 * particular ordering. One way to make the compiler aware of ordering is to
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | secure.txt | 5 kernel) are not TrustZone aware and run entirely in either the Normal
7 TrustZone aware and need to be able to determine whether devices are
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-subdev-g-client-cap.rst | 85 - The client is aware of streams. Setting this flag enables the use
90 - The client is aware of the :c:type:`v4l2_subdev_frame_interval`
|
| /linux/drivers/net/ethernet/microchip/lan966x/ |
| H A D | lan966x_vlan.c | 152 /* When the interface is in host mode, the interface should not be vlan aware
202 /* If port is vlan-aware and tagged, drop untagged and priority in lan966x_vlan_port_apply()
330 /* Configure the CPU port to be vlan aware */ in lan966x_vlan_init()
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 103 It is completely unreasonable for an application to be aware whether
188 5.2 Integrity-Aware Filesystem
191 A filesystem that is integrity-aware can prepare I/Os with IMD
|
| /linux/Documentation/locking/ |
| H A D | futex-requeue-pi.rst | 53 In order to support PI-aware pthread_condvar's, the kernel needs to
106 to be requeued to a PI-aware futex. The implementation is the
|
| /linux/fs/zonefs/ |
| H A D | Kconfig | 9 device (e.g. host-managed or host-aware SMR disk drives) as files.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | transactional_memory.rst | 120 However, basic signal handlers don't need to be aware of transactions
123 Transaction-aware signal handlers can read the transactional register state
198 GDB and ptrace are not currently TM-aware. If one stops during a transaction,
|
| /linux/include/linux/mailbox/ |
| H A D | zynqmp-ipi-message.h | 13 * Client is supposed to be aware of this.
|
| /linux/Documentation/networking/dsa/ |
| H A D | sja1105.rst | 99 Time-aware scheduling
189 - VLAN-aware virtual links: these match on destination MAC address, VLAN ID and
304 driver asks for the VLAN ID and VLAN PCP when the port is under a VLAN-aware
312 - port was standalone and joins a bridge (VLAN-aware or VLAN-unaware)
315 - port was standalone, but another port joins a VLAN-aware bridge and this
|
| /linux/net/dsa/ |
| H A D | tag_sja1105.c | 186 /* Port is VLAN-aware, so there is a bridge somewhere (a single one, in sja1105_xmit_tpid()
198 * VLAN-aware in that case. in sja1105_xmit_tpid()
205 WARN_ONCE(1, "Port is VLAN-aware but cannot find associated bridge!\n"); in sja1105_xmit_tpid()
218 /* If the port is under a VLAN-aware bridge, just slide the in sja1105_imprecise_xmit()
220 * This works because we support a single VLAN-aware bridge in sja1105_imprecise_xmit()
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_mode_neon.rst | 13 * Don't sleep in your NEON code, and be aware that it will be executed with
81 The compiler is not aware of the special significance of kernel_neon_begin() and
|