Home
last modified time | relevance | path

Searched refs:another (Results 1 – 25 of 638) sorted by relevance

12345678910>>...26

/Linux-v5.4/Documentation/admin-guide/
Dnumastat.rst13 numa_miss A process wanted to allocate memory from another node,
17 but ended up with memory from another one.
21 other_node A process ran on this node and got memory from another node.
/Linux-v5.4/tools/power/cpupower/
DToDo7 RAM from HW on Intel SandyBridge -> another monitor?
8 - Add another c1e debug idle monitor
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-bus-i2c-devices-pca954x11 with an address that conflicts with another
12 device on another mux on the same parent bus.
/Linux-v5.4/Documentation/media/uapi/v4l/
Ddev-mem2mem.rst17 otherwise convert video data from one format into another format, in memory.
34 the hardware and reprogram it whenever another file handler gets access.
37 file handle is visible through another file handle).
Dvidioc-subscribe-event.rst106 another, and then receives an event telling it that that control
109 Since it can't tell whether that event was caused by another
/Linux-v5.4/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset60 PF device is being recovered in another guest.
66 another message is sent to the guests to re-enable the VFs.
79 PF device is being recovered in another guest.
85 another message is sent to the guests to re-enable the VFs.
/Linux-v5.4/Documentation/admin-guide/namespaces/
Dcompatibility-list.rst31 other object in another namespace.
36 access permissions to files, belonging to user 10 in another
/Linux-v5.4/Documentation/RCU/
Drculist_nulls.txt61 "If the object is moved from one list to another list in-between the
75 from a chain, and inserted into another chain. If new chain was empty
118 to another chain) checking the final 'nulls' value if
144 * We probably met an item that was moved to another chain.
/Linux-v5.4/Documentation/devicetree/bindings/watchdog/
Daspeed-wdt.txt20 This is useful in situations where another watchdog engine on chip is
34 - none: No reset is performed on timeout. Assumes another watchdog
/Linux-v5.4/drivers/staging/pi433/
DTODO4 -> Replace this with another interface, hints are welcome!
/Linux-v5.4/Documentation/devicetree/bindings/rng/
Dmicrochip,pic32-rng.txt4 another true random number generator.
/Linux-v5.4/tools/perf/Documentation/
Dperf-archive.txt16 buildids found so that analysis of perf.data contents can be possible on another
/Linux-v5.4/Documentation/networking/
Dx25.txt23 implementation is being done as part of another protocol project (SNA) and
26 Just when you thought that it could not become more confusing, another
/Linux-v5.4/Documentation/i2c/
Dslave-eeprom-backend.rst14 notification when another master changed the content.
/Linux-v5.4/Documentation/devicetree/bindings/firmware/
Dcznic,turris-mox-rwtm.txt7 This device tree node should be used on Turris Mox, or potentially another A3700
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt10 another capabilities like L2 TLB or block-fetch buffers to minimize translation
40 another gate clock other core (usually main gate clock
/Linux-v5.4/Documentation/filesystems/ext4/
Dmmp.rst15 filesystem is active on another machine and the open fails. If the MMP
22 MMP sequence number, then another node (node B) has mounted the
/Linux-v5.4/drivers/ipack/
DKconfig11 are IndustryPack carrier boards, which interface another bus (such as
/Linux-v5.4/Documentation/devicetree/bindings/memory-controllers/
Dmvebu-sdram-controller.txt4 differs from one SoC variant to another, but they also share a number
/Linux-v5.4/drivers/infiniband/ulp/srpt/
DKconfig9 a block storage device on another host (target) over a network
/Linux-v5.4/tools/memory-model/litmus-tests/
DLB+fencembonceonce+ctrlonceonce.litmus11 * another control dependency and order would still be maintained.)
/Linux-v5.4/Documentation/admin-guide/sysctl/
Dindex.rst86 or other subdirs in another setup. If you see another dir, I'd
/Linux-v5.4/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt14 problems (hard to tell if i2c issues were caused by one master, another, or
51 - wait-retry-us: we'll attempt another claim after this many microseconds.
/Linux-v5.4/Documentation/trace/
Dring-buffer-design.txt64 but a writer may interrupt another writer, but it must finish writing
81 same time, nor can a reader preempt/interrupt another reader. A reader
84 on another processor to do so. A reader may read on its own processor
88 But a reader can read the buffer at the same time (on another processor)
210 writer stack. A writer that preempts another writer will not move the
218 transaction. If another write happens it must finish before continuing
282 committed without preempting another write. When a write that
283 preempted another write is committed, it only becomes a pending commit
344 The buffer is considered empty until another full commit finishes.
667 it will never go back on it unless a reader does another swap with the
/Linux-v5.4/drivers/infiniband/sw/siw/
DKconfig9 adapter or with another system running the SIW driver.

12345678910>>...26