Searched full:different (Results 1 – 25 of 4790) sorted by relevance
12345678910>>...192
| /Linux-v5.4/Documentation/process/ |
| D | stable-api-nonsense.rst | 64 - Depending on the version of the C compiler you use, different kernel
65 data structures will contain different alignment of structures, and
66 possibly include different functions in different ways (putting
68 isn't that important, but the different data structure padding is
72 different things can be assumed by the kernel:
74 - different structures can contain different fields
77 - Memory within the kernel can be aligned in different ways,
80 - Linux runs on a wide range of different processor architectures.
89 different Linux distributions and the number of different supported
91 different build options on different releases. Also realize that each
[all …]
|
| /Linux-v5.4/tools/testing/selftests/net/forwarding/ |
| D | tc_vlan_modify.sh | 108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | vcpudispatch_stats.txt | 8 scenarios, vcpus may be dispatched on a different processor chip (away
28 3. number of times this vcpu was dispatched on a different processor core
30 4. number of times this vcpu was dispatched on a different chip
31 5. number of times this vcpu was dispatches on a different socket/drawer
37 7. number of times this vcpu was dispatched in a different node
62 physical cpu as the last time. 2683 were on a different core, but within
63 the same chip, while 30 dispatches were on a different chip compared to
|
| /Linux-v5.4/Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces.
10 in different other namespaces (the rows):
28 other task living in a different namespace via a shared filesystem
33 2. Intentionally, two equal user IDs in different user namespaces
40 from different user namespaces should not access the same IPC objects
|
| /Linux-v5.4/include/uapi/linux/ |
| D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /Linux-v5.4/drivers/gpu/drm/msm/ |
| D | NOTES | 3 In the current snapdragon SoC's, we have (at least) 3 different
20 with N different kms devices from xf86-video-freedreno. Plus, it
25 So, the approach is one drm driver, with some modularity. Different
27 And one or more 'struct msm_gpu' for the various different gpu sub-
57 than needing a different implementation for DTV, DSI, etc. (Ie. the
58 register interface is same, just different bases.)
|
| /Linux-v5.4/Documentation/virt/ |
| D | paravirt_ops.rst | 7 Linux provides support for different hypervisor virtualization technologies.
8 Historically different binary kernels would be required in order to support
9 different hypervisors, this restriction was removed with pv_ops.
10 Linux pv_ops is a virtualization API which enables support for different
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | colorspaces.rst | 27 the human eye has color receptors that are sensitive to three different
30 different wavelengths, so instead of RGB we would be using the
41 possible that different SPDs will result in the same stimulation of
43 of the light is different.
75 different wavelengths, the combination of which will stimulate the color
81 Different display devices will have different primaries and some
84 different display technologies or uses. To define a colorspace you need
157 mix of different standards also led to very confusing naming conventions
|
| D | format.rst | 20 Different devices exchange different kinds of data with applications,
22 within one kind many different formats are possible, in particular there is an
51 example, when the new standard uses a different number of scan lines,
54 multiple file descriptors which grabbed different logical streams
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | rt5663.txt | 23 Based on the different PCB layout, add the manual offset value to
24 compensate the DC offset for each L and R channel, and they are different
38 should compensate different DC offset to avoid the pop sound, and it is
39 also different between headphone and headset. In the example, the
|
| /Linux-v5.4/tools/testing/ktest/examples/ |
| D | test.conf | 8 # BOX can be different than foo, if the machine BOX has
9 # multiple partitions with different systems installed. For example,
12 # machine, which may be different between which system the machine
55 # The following files each handle a different test case.
|
| /Linux-v5.4/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | cache.json | 5 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
6 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
11 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
12 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
17 …": "The processor's data cache was reloaded from another chip's L4 on a different Node or Group (D…
18 …": "The processor's data cache was reloaded from another chip's L4 on a different Node or Group (D…
107 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
108 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
|
| D | frontend.json | 89 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
90 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
95 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
96 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
101 … processor's Instruction cache was reloaded from another chip's L4 on a different Node or Group (D…
102 … processor's Instruction cache was reloaded from another chip's L4 on a different Node or Group (D…
203 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
204 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
293 …d into the TLB with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
299 …ded into the TLB with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 4 The OMAP mailbox hardware facilitates communication between different processors
17 and tx interrupt source per h/w fifo. Communication between different processors
23 instance. DRA7xx has multiple instances with different number of h/w fifo queues
24 and interrupt lines between different instances. The interrupt lines can also be
25 routed to different processor sub-systems on DRA7xx as they are routed through
29 all these clusters are multiplexed and routed to different processor subsystems
78 Each child node should have a unique node name across all the different
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-port | 7 distinguish different ports under same FPGA device.
13 Description: Read-only. User can program different PR bitstreams to FPGA
14 Accelerator Function Unit (AFU) for different functions. It
22 Description: Read-only. It reports the APx (AFU Power) state, different APx
23 means different throttling level. When reading this file, it
|
| /Linux-v5.4/tools/memory-model/litmus-tests/ |
| D | IRIW+poonceonces+OnceOnce.litmus | 8 * needed to cause two different reading processes to agree on the order
9 * of a pair of writes, where each write is to a different variable by a
10 * different process?
|
| D | IRIW+fencembonceonces+OnceOnce.litmus | 8 * cause two different reading processes to agree on the order of a pair
9 * of writes, where each write is to a different variable by a different
|
| D | README | 26 sufficient to cause two different reading processes to agree on
27 the order of a pair of writes, where each write is to a different
28 variable by a different process? This litmus test is forbidden
34 needed to cause two different reading processes to agree on the
35 order of a pair of writes, where each write is to a different
36 variable by a different process?
220 to a different variable ("d"), and both accesses are reads ("RR").
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | concepts.rst | 25 address ranges. Besides, different CPU architectures, and even
26 different implementations of the same architecture have different views
103 Often hardware poses restrictions on how different physical memory
115 architectures define all zones, and requirements for DMA are different
116 for different platforms.
123 different access latency depending on the "distance" from the
161 different types of data. It can be kernel internal data structures,
|
| /Linux-v5.4/tools/testing/selftests/bpf/verifier/ |
| D | unpriv.c | 219 "unpriv: spill/fill of different pointers stx",
237 .errstr = "same insn cannot be used with different pointers",
241 "unpriv: spill/fill of different pointers stx - ctx and sock",
275 "unpriv: spill/fill of different pointers stx - leak sock",
301 //.errstr = "same insn cannot be used with different pointers",
306 "unpriv: spill/fill of different pointers stx - sock and ctx (read)",
334 .errstr = "same insn cannot be used with different pointers",
338 "unpriv: spill/fill of different pointers stx - sock and ctx (write)",
367 //.errstr = "same insn cannot be used with different pointers",
372 "unpriv: spill/fill of different pointers ldx",
[all …]
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | reproducible-builds.rst | 78 generate a different temporary key for each build, resulting in the
114 vDSO's debug information may be identical even for different kernel
116 packages for the different kernel versions.
118 To avoid this, you can make the vDSO different for different
|
| /Linux-v5.4/Documentation/ABI/ |
| D | README | 4 interfaces should be used by userspace programs in different ways.
6 We have four different levels of ABI stability, as shown by the four
7 different subdirectories in this location. Interfaces may change levels
10 The different levels of stability are:
|
| /Linux-v5.4/Documentation/ioctl/ |
| D | botching-up-ioctls.rst | 11 memory on completely different GPUs is a futile effort. So nowadays every
40 64-bit. Having a different structure size hurts when passing arrays of
49 and pointres of different sizes.
137 derived from different clock domains like your main system clock (provided
173 for different objects and other resources to userspace. Doing that right
183 * Ensure that you have sufficient insulation between different clients. By
195 to know whether it has seen an imported object from a different process
|
| /Linux-v5.4/Documentation/gpu/ |
| D | vgaarbiter.rst | 15 when these devices are trying to be accessed by different userspace clients
27 arbiter then enables/disables the decoding on different devices of the VGA
137 any resource on a different bus segment, since P2P bridges don't differentiate
146 For instance, in x86 if two devices on the same bus want to lock different
147 resources, both will succeed (lock). If devices are in different buses and
148 trying to lock different resources, only the first who tried succeeds. ::
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | erofs.txt | 4 EROFS file-system stands for Enhanced Read-Only File System. Different
26 - 2 inode versions for different requirements:
75 Different from other read-only file systems, an EROFS volume is designed
85 may not. All metadatas can be now observed in two different spaces (views):
132 proper alignes, and they could be optional for different data mappings,
140 header. Large xattrs or xattrs shared by many different files can be
|
12345678910>>...192
