Searched full:aware (Results 1 – 25 of 196) sorted by relevance
12345678
| /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
|
| /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
|
| /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
|
| /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
|
| /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
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 12 be aware of changes that can occur before these interfaces move to
|
| /Documentation/translations/zh_CN/ |
| D | glossary.rst | 18 * EAS: 能耗感知调度。（Energy Aware Scheduling）
|
| /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
|
| /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
|
| D | microchip,sparx5.yaml | 19 TCAM-based frame processing using versatile content aware processor
|
| /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`
|
| /Documentation/arch/mips/ |
| D | booting.rst | 11 Similar to the arch/arm case (b), a DT-aware bootloader is expected to
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 26 for there first. Be aware that newline characters will be taken into account
|
| /Documentation/timers/ |
| D | timers-howto.rst | 60 quirks you should be aware of.
71 it is something to be aware of.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | berlin,pinctrl.txt | 13 Be aware the Marvell Berlin datasheets use the keyword 'mode' for what
|
| /Documentation/networking/ |
| D | sctp.rst | 29 - lksctp can be built as statically or as a module. However, be aware that
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 20 underlying IP blocks changes in a way that software should be aware of.
|
| /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
|
| /Documentation/fb/ |
| D | metronomefb.rst | 26 can be compressed as long as your udev or hotplug script is aware of the need
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | melexis,mlx90632.yaml | 23 Be aware that electronics surrounding the sensor can increase ambient
|
| /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
|
| /Documentation/hwmon/ |
| D | asus_ec_sensors.rst | 42 The driver is aware of and reads the following sensors:
|
| /Documentation/arch/arm/ |
| 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
|
| /Documentation/admin-guide/pm/ |
| D | intel_uncore_frequency_scaling.rst | 62 SoCs with TPMI (Topology Aware Register and PM Capsule Interface)
76 SoCs with the support of TPMI (Topology Aware Register and PM Capsule
|
12345678