Home
last modified time | relevance | path

Searched +full:foo +full:- +full:queue (Results 1 – 12 of 12) sorted by relevance

/Documentation/devicetree/bindings/misc/
Dintel,ixp4xx-ahb-queue-manager.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/misc/intel,ixp4xx-ahb-queue-manager.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
8 title: Intel IXP4xx AHB Queue Manager
11 - Linus Walleij <linus.walleij@linaro.org>
14 The IXP4xx AHB Queue Manager maintains queues as circular buffers in
18 queues from the queue manager with foo-queue = <&qmgr N> where the
19 &qmgr is a phandle to the queue manager and N is the queue resource
20 number. The queue resources available and their specific purpose
[all …]
/Documentation/filesystems/
Dinotify.txt8 --Deleted obsoleted interface, just refer to manpages for user interface.
21 Q: What is the design decision behind using an-fd-per-instance as opposed to
22 an fd-per-watch?
24 A: An fd-per-watch quickly consumes more file descriptors than are allowed,
26 select()-able. Yes, root can bump the per-process fd limit and yes, users
29 spaces is thus sensible. The current design is what user-space developers
32 thousand times is silly. If we can implement user-space's preferences
33 cleanly--and we can, the idr layer makes stuff like this trivial--then we
37 item to block on, which is mapped to a single queue of events. The single
38 fd returns all watch events and also any potential out-of-band data. If
[all …]
/Documentation/power/
Druntime_pm.rst5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
69 dev->driver->pm directly (if present).
73 and bus type. Moreover, the high-priority one will always take precedence over
[all …]
/Documentation/networking/
Dsnmp_counter.rst17 .. _RFC1213 ipInReceives: https://tools.ietf.org/html/rfc1213#page-26
30 .. _RFC1213 ipInDelivers: https://tools.ietf.org/html/rfc1213#page-28
41 .. _RFC1213 ipOutRequests: https://tools.ietf.org/html/rfc1213#page-28
60 .. _Explicit Congestion Notification: https://tools.ietf.org/html/rfc3168#page-6
73 .. _RFC1213 ipInHdrErrors: https://tools.ietf.org/html/rfc1213#page-27
81 .. _RFC1213 ipInAddrErrors: https://tools.ietf.org/html/rfc1213#page-27
98 .. _RFC1213 ipInUnknownProtos: https://tools.ietf.org/html/rfc1213#page-27
111 .. _RFC1213 ipInDiscards: https://tools.ietf.org/html/rfc1213#page-28
118 .. _RFC1213 ipOutDiscards: https://tools.ietf.org/html/rfc1213#page-28
125 .. _RFC1213 ipOutNoRoutes: https://tools.ietf.org/html/rfc1213#page-29
[all …]
Dfilter.txt5 ------------
12 BPF allows a user-space program to attach a filter onto any socket and
37 The biggest user of this construct might be libpcap. Issuing a high-level
38 filter command like `tcpdump -i em1 port 22` passes through the libpcap
40 via SO_ATTACH_FILTER to the kernel. `tcpdump -i em1 port 22 -ddd`
45 qdisc layer, SECCOMP-BPF (SECure COMPuting [1]), and lots of other places
48 [1] Documentation/userspace-api/seccomp_filter.rst
53 architecture for user-level packet capture. In Proceedings of the
56 CA, USA, 2-2. [http://www.tcpdump.org/papers/bpf-usenix93.pdf]
59 ---------
[all …]
Dbonding.txt7 Corrections, HA extensions : 2000/10/03-15 :
8 - Willy Tarreau <willy at meta-x.org>
9 - Constantine Gavrilov <const-g at xpert.com>
10 - Chad N. Tindel <ctindel at ieee dot org>
11 - Janice Girouard <girouard at us dot ibm dot com>
12 - Jay Vosburgh <fubar at us dot ibm dot com>
16 - Mitch Williams <mitch.a.williams at intel.com>
29 the original tools from extreme-linux and beowulf sites will not work
114 -----------------------------------------------
130 -------------------------------------
[all …]
/Documentation/core-api/
Datomic_ops.rst23 See :ref:`Documentation/process/volatile-considered-harmful.rst
28 :ref:`Documentation/core-api/local_ops.rst <local_ops>` for the semantics of
35 #define atomic_set(v, i) ((v)->counter = (i))
52 struct foo { atomic_t counter; };
55 struct foo *k;
59 return -ENOMEM;
60 atomic_set(&k->counter, 0);
70 #define atomic_read(v) ((v)->counter)
179 Don't even -think- about doing this without proper use of memory barriers,
305 Preceding a non-value-returning read-modify-write atomic operation with
[all …]
/Documentation/
Dmemory-barriers.txt19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Data dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]
DDMA-API-HOWTO.txt10 with example pseudo-code. For a concise description of the API, see
11 DMA-API.txt.
39 supports 64-bit addresses for main memory and PCI BARs, it may use an IOMMU
40 so devices only need to use 32-bit DMA addresses.
49 +-------+ +------+ +------+
52 C +-------+ --------> B +------+ ----------> +------+ A
54 +-----+ | | | | bridge | | +--------+
55 | | | | +------+ | | | |
58 +-----+ +-------+ +------+ +------+ +--------+
60 X +-------+ --------> Y +------+ <---------- +------+ Z
[all …]
/Documentation/translations/ko_KR/
Dmemory-barriers.txt2 This is a version of Documentation/memory-barriers.txt translated into Korean.
15 Documentation/memory-barriers.txt
39 일부 이상한 점들은 공식적인 메모리 일관성 모델과 tools/memory-model/ 에 있는
60 해당 배리어의 명시적 사용이 불필요해서 no-op 이 될수도 있음을 알아두시기
76 - 디바이스 오퍼레이션.
77 - 보장사항.
81 - 메모리 배리어의 종류.
82 - 메모리 배리어에 대해 가정해선 안될 것.
83 - 데이터 의존성 배리어 (역사적).
84 - 컨트롤 의존성.
[all …]
/Documentation/kernel-hacking/
Dlocking.rst37 +------------------------------------+------------------------------------+
41 +------------------------------------+------------------------------------+
43 +------------------------------------+------------------------------------+
45 +------------------------------------+------------------------------------+
47 +------------------------------------+------------------------------------+
49 +------------------------------------+------------------------------------+
51 +------------------------------------+------------------------------------+
57 +------------------------------------+------------------------------------+
61 +------------------------------------+------------------------------------+
63 +------------------------------------+------------------------------------+
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
56 Documentation/firmware-guide/acpi/debug.rst for more information about
119 Disable auto-serialization of AML methods
122 auto-serialization feature.
[all …]