Searched full:same (Results 1 – 25 of 1517) sorted by relevance
12345678910>>...61
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 9 all per-CPU defaults at the same time.
64 Description: internal kernel map of CPUs within the same core.
69 Description: human-readable list of CPUs within the same core.
75 Description: internal kernel map of the CPUs sharing the same physical_package_id.
80 Description: human-readable list of CPUs sharing the same physical_package_id.
86 Description: internal kernel map of CPUs within the same die.
94 Description: human-readable list of CPUs within the same die.
99 Description: internal kernel map of CPUs within the same cluster.
103 Description: human-readable list of CPUs within the same cluster.
108 Description: internal kernel map of cpuX's hardware threads within the same
[all …]
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same
35 system woke up, who cares? It'll still work the same when you type on
39 devices. The effect is exactly the same as if the device really had
47 interrupts a power session will have the same effect. For example,
83 same thing that happens whenever a USB device is reset.) If the
85 same descriptors as before, including the Vendor and Product IDs, then
86 the kernel continues to use the same device structure. In effect, the
90 The same thing happens if the host controller is in the expected state
125 have the same persistent volume associated with the device. As such
142 to make sure the USB device hasn't been changed; that is, the same
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | zswap.rst | 107 Some of the pages in zswap are same-value filled pages (i.e. contents of the
108 page have same value or repetitive pattern). These pages include zero-filled
110 checked if it is a same-value filled page before compressing it. If true, the
111 compressed length of the page is set to zero and the pattern or same-filled
114 Same-value filled pages identification feature is enabled by default and can be
122 When zswap same-filled page identification is disabled at runtime, it will stop
123 checking for the same-value filled pages during store operation.
124 In other words, every page will be then considered non-same-value filled.
125 However, the existing pages which are marked as same-value filled pages remain
129 ability to efficiently store same-filled pages without enabling the whole
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 18 - clock-names: names of the clocks listed in clocks property in the same
36 - clock-names: names of the clocks listed in clocks property in the same
40 - reset-names: names of the resets listed in resets property in the same
50 the same order.
53 - reset-names: names of the resets listed in resets property in the same
62 the same order.
65 the same order
68 - clock-names: names of the clocks listed in clocks property in the same
78 the same order.
82 - clock-names: names of the clocks listed in clocks property in the same
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | client-identifier.rst | 57 server to distinguish successive boot epochs of the same client.
95 If distinct clients present the same "co_ownerid" string and use
96 the same principal (for example, AUTH_SYS and UID 0), a server is
97 unable to tell that the clients are not the same. Each distinct
102 If distinct clients present the same "co_ownerid" string and use
104 to operate normally but reject subsequent clients with the same
128 the client's UTS node name (the same node name, incidentally, that
140 client instances with the same host name.
191 use the same lease for operations covered by all "sec=" settings.
206 migration by presenting the same "client_owner4" to all servers it
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 23 to be defined in the UAPI header, aliased to the same value.
77 via the same trace points as for regular XDP programs.
85 will be transmitted *out* of that same interface. Do note, though, that
87 ``XDP_TX`` is actually turned into the same action as an ``XDP_REDIRECT`` to
88 that same interface (i.e., it will only work if the driver has support for the
92 in batches. The batch size defaults to 64 packets (which is same as the
102 pages of the same size as the batch size. Each memory page will be initialised
|
| /Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 35 program order (po) relation (on the same CPU). It guarantees that
42 stores (all po-earlier instructions) on the same CPU are completed
43 before any po-later instruction is executed on the same CPU.
44 It also guarantees that all po-earlier stores on the same CPU
50 stores (all po-earlier instructions) on the same CPU are completed
52 stores on the same CPU and all propagated stores from other CPUs
58 stores (all po-later instructions) on the same CPU are
60 po-later stores on the same CPU must propagate to all other CPUs
|
| /Documentation/arch/x86/ |
| D | sva.rst | 11 same virtual addresses avoiding the need for software to translate virtual
18 (PRI) allow devices to function much the same way as the CPU handling
98 with the same PASID. The platform IOMMU uses the PASID in the transaction to
104 thread can interact with a device. Threads that belong to the same
105 process share the same page tables, thus the same MSR value.
114 device but finds no PASID for this process. Subsequent binds of the same, or
115 other devices will share the same PASID.
129 longer has the same address space that it had when the device was opened.
131 On clone(2) the new task shares the same address space, so will be
161 * Multiple processes can separately mmap() the same portal, in
[all …]
|
| D | tsx_async_abort.rst | 17 the same uarch data structures as in MDS, with same scope of exposure i.e.
18 same-thread and cross-thread. This issue affects all current processors that
69 …0 0 0 HW default Yes Same as MDS Same as MDS
84 … 0 0 0 HW default Yes Same as MDS Same as MDS
87 … 0 1 1 Enabled Yes None Same as MDS
99 …0 0 0 HW default Yes Same as MDS Same as MDS
|
| /Documentation/networking/ |
| D | sysfs-tagging.rst | 11 namespace active multiple devices with the same name can show up in
12 the same directory, ouch!
15 namespaces to see the same interface that is currently presented in
|
| /Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | 9 Any subsequently received response can be read from this same
24 Any subsequently received response can be read from this same
27 from this same entry too if it arrived within the configured
77 Any subsequently received response can be read from this same
101 Any subsequently received response can be read from this same
105 from this same entry too if it arrived within the configured
|
| /Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 31 2. number of times this vcpu was dispatched on the same processor as last
34 as last time, but within the same chip
68 statistics were enabled. 4126 of those dispatches were on the same
70 the same chip, while 30 dispatches were on a different chip compared to
|
| /Documentation/devicetree/bindings/net/ |
| D | nixge.txt | 8 information of registers in the same order as described by reg-names.
14 - phy-mode: See ethernet.txt file in the same directory.
20 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
22 - phy-handle: See ethernet.txt file in the same directory.
|
| D | lpc-eth.txt | 9 - phy-mode: See ethernet.txt file in the same directory. If the property is
15 phy.txt in the same directory
|
| /Documentation/mm/ |
| D | numa.rst | 33 attached to the same cell will experience faster access times and higher
41 [cache misses] to be to "local" memory--memory on the same cell, if any--or
59 a given node will see the same local memory access times and bandwidth.
81 fall back to the same zone type on a different node, or to a different zone
82 type on the same node. This is an important consideration because some zones,
85 from the same node before using remote nodes which are ordered by NUMA distance.
123 closest available memory. This is a consequence of the same mechanism that
147 specified CPU. Again, this is the same node from which default, local page
|
| /Documentation/virt/kvm/devices/ |
| D | vfio.rst | 36 KVM_DEV_VFIO_GROUP_ADD: same as KVM_DEV_VFIO_FILE_ADD for group fd only
38 KVM_DEV_VFIO_GROUP_DEL: same as KVM_DEV_VFIO_FILE_DEL for group fd only
58 callback. It is the same for device file descriptor via character device
|
| /Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 35 words, user 10 in one user namespace shouldn't have the same
39 The same is true for the IPC namespaces being shared - two users
40 from different user namespaces should not access the same IPC objects
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 9 workloads may benefit from running on the same core as they don't need the same
17 Threads of the same core. MDS and L1TF are examples of such attacks. The only
36 on the same core. The core scheduler uses this information to make sure that
37 tasks that are not in the same group never run simultaneously on a core, while
83 same core-sched group.
96 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust
101 trusted (same cookie) at any point in time. Kernel threads are assumed trusted.
108 highest priority task with the same cookie is selected if there is one runnable
109 in their individual run queues. If a task with same cookie is not available,
152 assigning them a tag that is the same cookie value.
|
| /Documentation/power/ |
| D | swsusp-and-swap-files.rst | 7 The Linux kernel handles swap files almost in the same way as it handles swap
45 by the same application that determines the swap file's header offset using the
56 Now, swsusp will use the swap file in the same way in which it would use a swap
61 the location of its header need not be the same as before. Thus every time
|
| /Documentation/userspace-api/ |
| D | futex2.rst | 75 shares the same memory space and the virtual address of the futex will be the
76 same for all processes. This allows for optimizations in the kernel. To use
78 flag. For processes that doesn't share the same memory space and therefore can
79 have different virtual addresses for the same futex (using, for instance, a
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sti-asoc-card.txt | 20 - clock-names: name of the clocks listed in clocks property in the same order
22 - reg: CPU DAI IP Base address and size entries, listed in same
26 the same order.
28 - interrupts: CPU_DAI interrupt line, listed in the same order than the
31 - dma: CPU_DAI DMA controller phandle and DMA request line, listed in the same
39 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| D | fsl,audmix.txt | 11 the same TDM frame format. This output is used to drive the serial DAC TDM
21 input streams must have same audio sample rate with same number of channels
|
| /Documentation/devicetree/bindings/media/ |
| D | st,st-hva.txt | 7 - reg-names: names of the registers listed in registers property in the same
13 - clock-names: names of the clocks listed in clocks property in the same order.
|
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 19 world value is the same as specified for the Normal world by the
42 same value as "status"; if "status" is not specified either then
65 its console output. The syntax is the same as for /chosen/stdout-path.
69 /chosen/stdout-path instead (that is, use the same device as the
|
| /Documentation/kbuild/ |
| D | reproducible-builds.rst | 5 It is generally desirable that building the same source code with
6 the same set of tools is reproducible, i.e. the output is always
7 exactly the same. This makes it possible to verify that the build
103 the random seed in ``scripts/basic/randstruct.seed`` so the same
127 ``git reset HEAD^``, even if the code is the same, the
|
12345678910>>...61