Searched full:behavior (Results 1 – 25 of 372) sorted by relevance
12345678910>>...15
| /Documentation/process/ |
| D | code-of-conduct.rst | 19 Examples of behavior that contributes to creating a positive environment
29 Examples of unacceptable behavior by participants include:
44 Maintainers are responsible for clarifying the standards of acceptable behavior
46 any instances of unacceptable behavior.
67 Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 32 The GFP flags control the allocators behavior. They tell what memory
88 GFP flags and reclaim behavior
113 **default** page allocator behavior is used. That means that not costly
115 that behavior so failures have to be checked properly by callers
118 * ``GFP_KERNEL | __GFP_NORETRY`` - overrides the default allocator behavior
124 behavior and all allocation requests try really hard. The request
128 * ``GFP_KERNEL | __GFP_NOFAIL`` - overrides the default allocator behavior
|
| D | dma-attributes.rst | 16 behavior.
26 behavior.
44 attribute and exhibit default behavior.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-dust.rst | 4 This target emulates the behavior of bad sectors at arbitrary
10 requests on specific blocks (to emulate the behavior of a hard disk
13 When the failure behavior is enabled (i.e.: when the output of
22 This emulates the "remapped sector" behavior of a drive with bad
71 Check the status of the read behavior ("bypass" indicates that all I/O
111 To enable the "fail read on bad block" behavior, send the "enable" message::
129 therefore emulating the "remap" behavior of hard disk drives::
302 This target seeks to provide a device that can exhibit the behavior
|
| /Documentation/translations/zh_CN/rust/ |
| D | coding-guidelines.rst | 113 /// Calling this method on [`None`] is *[undefined behavior]*.
115 /// [undefined behavior]: https://doc.rust-lang.org/reference/behavior-considered-undefined.html
|
| /Documentation/trace/rv/ |
| D | runtime-verification.rst | 13 the system behavior.
16 behavior of the monitored system, without the pitfalls of developing models
28 undesired) behavior, and the trace of the actual system.
56 event occurrence to the enforcement of the correct behavior to the extreme
111 For further information about modeling of Linux kernel behavior using automata,
|
| /Documentation/admin-guide/ |
| D | jfs.rst | 16 iocharset=none specifies the default behavior explicitly.
34 previously specified in order to restore normal behavior.
|
| D | serial-console.rst | 37 The behavior is well defined when each device type is mentioned only once.
48 The behavior is more complicated when the same device type is defined more
70 because of the default behavior when no console device is specified,
|
| /Documentation/gpu/amdgpu/ |
| D | ras.rst | 14 RAS Reboot Behavior for Unrecoverable Errors
18 :doc: AMDGPU RAS Reboot Behavior for Unrecoverable Errors
|
| /Documentation/ABI/testing/ |
| D | dev-kmsg | 63 the special behavior this device has. The device allows to read
67 Because of the non-standard behavior also the error values are
69 is returned for other operations, e.g. SEEK_CUR. This behavior
|
| D | sysfs-kernel-reboot | 5 Description: Interface to set the kernel reboot behavior, similarly to
|
| /Documentation/scheduler/ |
| D | sched-ext.rst | 5 sched_ext is a scheduler class whose behavior can be defined by a set of BPF
17 The default scheduling behavior is restored anytime an error is detected,
136 * Note that this implementation has exactly the same behavior as the
137 * default ops.select_cpu implementation. The behavior of the scheduler
161 * Note that this implementation has exactly the same behavior as the
163 * to SCX_DSQ_GLOBAL. The behavior of the scheduler would be exactly same
|
| /Documentation/cdrom/ |
| D | cdrom-standard.rst | 27 all these different devices has also allowed the behavior of each
29 This divergence of behavior has been very significant for CD-ROM
35 maintain uniform behavior across all the Linux CD-ROM drivers.
37 This document describes an effort to establish Uniform behavior across
66 importantly, it appeared that the behavior of the `standard` commands
73 behavior was usually different.
94 **one** Linux CD-ROM interface with consistent behavior for all
123 importantly, this led to the divergence of behavior, which has already
127 CD-ROM drive behavior, and to provide a common set of services to the various
165 place where the behavior of all CD-ROM-devices is defined and
[all …]
|
| /Documentation/hwmon/ |
| D | drivetemp.rst | 38 drives as well. The same behavior is observed if the 'hdtemp' or 'smartd'
44 drives experience similar behavior.
|
| /Documentation/tools/rtla/ |
| D | index.rst | 8 behavior on specific hardware.
|
| /Documentation/arch/arm/ |
| D | mem_alignment.rst | 30 To change the alignment trap behavior, simply echo a number into
34 bit behavior when set
|
| /Documentation/filesystems/ |
| D | virtiofs.rst | 48 atime behavior
52 are ignored. The atime behavior for virtiofs is the same as the
|
| /Documentation/devicetree/bindings/mfd/ |
| D | atmel-matrix.txt | 4 behavior (master/slave priorities, undefined burst length type, ...)
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 9 Because VM is getting complex (one of reasons is memcg...), memcg's behavior
10 is complex. This is a document for memcg's internal behavior.
114 But brief explanation of the behavior of memcg around shmem will be
152 (Memory behavior under GB and Memory behavior under MB shows very
|
| /Documentation/devicetree/bindings/soc/nuvoton/ |
| D | nuvoton,gfxi.yaml | 15 that analyzes Graphics core behavior and provides information in registers.
|
| /Documentation/arch/x86/ |
| D | microcode.rst | 132 unpredictable behavior.
158 To be paranoid and get predictable behavior, the OS can choose to set
182 pulled into NMI, that can cause unpredictable behavior due to the
192 real workloads. Late loading behavior depends on what the base patch on
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-misc-cp500 | 14 bitstream on reset. Normal FPGA behavior and default is to keep
|
| /Documentation/dev-tools/ |
| D | ubsan.rst | 3 Undefined Behavior Sanitizer - UBSAN
8 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
|
| /Documentation/mm/ |
| D | z3fold.rst | 27 depend on MMU enabled and provides more predictable reclaim behavior
|
| /Documentation/networking/ |
| D | openvswitch.rst | 63 but the forwarding behavior is correct. (If userspace can
65 forwarding behavior, then it could set up a flow anyway.)
130 The behavior when using overlapping wildcarded flows is undefined. It is the
134 some but not all of them. However, this behavior may change in future versions.
188 802.1Q header) and it could cause the application's behavior to change
|
12345678910>>...15