Searched full:aware (Results 1 – 25 of 648) sorted by relevance
12345678910>>...26
| /linux-6.12.1/Documentation/mm/ |
| D | transhuge.rst | 59 pmd_offset. It's trivial to make the code transparent hugepage aware
64 hugepage aware.
72 Example to make mremap.c transparent hugepage aware with a one liner
86 Locking in hugepage aware code
89 We want as much code as possible hugepage aware, as calling
92 To make pagetable walks huge pmd aware, all you need to do is to call
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| 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-6.12.1/tools/testing/selftests/kvm/aarch64/ |
| 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-6.12.1/tools/testing/selftests/drivers/net/mlxsw/ |
| 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"
|
| 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-6.12.1/Documentation/admin-guide/mm/ |
| 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-6.12.1/Documentation/scheduler/ |
| 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-6.12.1/include/linux/ |
| 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-6.12.1/Documentation/mm/damon/ |
| D | index.rst | 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
|
| D | design.rst | 32 overhead/accuracy control and access-aware system operations on top of the
272 One common purpose of data access monitoring is access-aware system efficiency
546 The programming interface for kernel space data access-aware applications.
549 access-aware applications using DAMON's core features. For this, DAMON exposes
564 for general purpose DAMON control and special purpose data access-aware system
566 user space. The user space can build their efficient data access-aware
597 Special-Purpose Access-aware Kernel Modules
603 in runtime. For each special-purpose system-wide data access-aware system
|
| /linux-6.12.1/Documentation/devicetree/bindings/bus/ |
| 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-6.12.1/arch/arm/mach-sa1100/include/mach/ |
| 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-6.12.1/include/asm-generic/ |
| 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-6.12.1/drivers/gpu/drm/ |
| D | drm_self_refresh_helper.c | 31 * &drm_connector_state.self_refresh_aware to true at runtime if it is SR-aware
47 * connectors must be SR aware and all will enter/exit SR mode at the same time.
49 * If the crtc and connector are SR aware, but the panel connected does not
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| 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-6.12.1/Documentation/devicetree/bindings/arm/ |
| 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-6.12.1/arch/powerpc/platforms/cell/ |
| D | cpufreq_spudemand.c | 3 * spu aware cpufreq governor for the cell processor
132 MODULE_DESCRIPTION("SPU-aware cpufreq governor for the cell processor");
|
| /linux-6.12.1/Documentation/timers/ |
| D | timers-howto.rst | 60 quirks you should be aware of.
71 it is something to be aware of.
|
| /linux-6.12.1/Documentation/locking/ |
| 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-6.12.1/fs/zonefs/ |
| D | Kconfig | 9 device (e.g. host-managed or host-aware SMR disk drives) as files.
|
| /linux-6.12.1/Documentation/block/ |
| 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-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-block | 215 segment. For a zoned block device, either host-aware or
441 "host-managed" or "host-aware"), the sum of zones belonging to
480 "host-managed" or "host-aware"), the sum of zones belonging to
560 block device ("host-aware" or "host-managed" zone model). For
735 "host-aware"). This value is always 0 for regular block devices.
745 devices and "host-aware" or "host-managed" for zoned block
746 devices. The characteristics of host-aware and host-managed
|
| /linux-6.12.1/include/linux/mailbox/ |
| D | zynqmp-ipi-message.h | 13 * Client is supposed to be aware of this.
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | abi-testing.rst | 12 be aware of changes that can occur before these interfaces move to
|
| /linux-6.12.1/Documentation/arch/powerpc/ |
| 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,
|
12345678910>>...26