Home
last modified time | relevance | path

Searched +full:foo +full:- +full:queue (Results 1 – 18 of 18) 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.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
13 - Deleted obsoleted interface, just refer to manpages for user interface.
29 What is the design decision behind using an-fd-per-instance as opposed to
30 an fd-per-watch?
33 An fd-per-watch quickly consumes more file descriptors than are allowed,
35 select()-able. Yes, root can bump the per-process fd limit and yes, users
38 spaces is thus sensible. The current design is what user-space developers
41 thousand times is silly. If we can implement user-space's preferences
42 cleanly--and we can, the idr layer makes stuff like this trivial--then we
[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.rst1 .. SPDX-License-Identifier: GPL-2.0
3 .. _networking-filter:
10 ------
17 ------------
24 BPF allows a user-space program to attach a filter onto any socket and
49 The biggest user of this construct might be libpcap. Issuing a high-level
50 filter command like `tcpdump -i em1 port 22` passes through the libpcap
52 via SO_ATTACH_FILTER to the kernel. `tcpdump -i em1 port 22 -ddd`
57 qdisc layer, SECCOMP-BPF (SECure COMPuting [1]_), and lots of other places
60 .. [1] Documentation/userspace-api/seccomp_filter.rst
[all …]
Dbonding.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
35 the original tools from extreme-linux and beowulf sites will not work
119 -----------------------------------------------
[all …]
/Documentation/mm/
Dphysical_memory.rst1 .. SPDX-License-Identifier: GPL-2.0
8 architecture-independent abstraction to represent the physical memory. This
13 `Non-Uniform Memory Access (NUMA)
14 <https://en.wikipedia.org/wiki/Non-uniform_memory_access>`_.
15 With multi-core and multi-socket machines, memory may be arranged into banks
42 memory with DMA specific requirements (Documentation/core-api/dma-api.rst),
47 ``CONFIG_ZONE_DMA32`` configuration options. Some 64-bit platforms may need
59 only on some 32-bit architectures and is enabled with ``CONFIG_HIGHMEM``.
69 Documentation/admin-guide/mm/memory-hotplug.rst for additional details.
85 For example, with 32-bit kernel on an x86 UMA machine with 2 Gbytes of RAM the
[all …]
/Documentation/bpf/
Dverifier.rst32 After kernel function call, R1-R5 are reset to unreadable and
35 Since R6-R9 are callee saved, their state is preserved across the call.
40 bpf_call foo
72 stack bounds, which are [-MAX_BPF_STACK, 0). In this example offset is 8,
78 Classic BPF verifier does similar check with M[0-15] memory slots.
81 bpf_ld R0 = *(u32 *)(R10 - 4)
85 Though R10 is correct read-only register and has type PTR_TO_STACK
86 and R10 - 4 is within stack bounds, there were no stores into that location.
88 Pointer register spill/fill is tracked as well, since four (R6-R9)
91 Allowed function calls are customized with bpf_verifier_ops->get_func_proto()
[all …]
/Documentation/doc-guide/
Dsphinx.rst12 .. _Sphinx: http://www.sphinx-doc.org/
16 documentation comments, or kernel-doc comments, from source files. Usually these
18 kernel-doc comments have some special structure and formatting, but beyond that
34 :ref:`sphinx-pre-install` for further details.
42 Sphinx inside a virtual environment, using ``virtualenv-3``
56 (sphinx_latest) $ pip install -r Documentation/sphinx/requirements.txt
64 ------------
75 --------------------
86 ------------------------
95 The former was the only option for pre-6.1 kernel documentation and it
[all …]
/Documentation/core-api/
Ddma-api-howto.rst10 with example pseudo-code. For a concise description of the API, see
11 Documentation/core-api/dma-api.rst.
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/
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 - Address-dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
Dcgroup-v2.rst1 .. _cgroup-v2:
11 conventions of cgroup v2. It describes all userland-visible aspects
14 v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgroup-v1>`.
19 1-1. Terminology
20 1-2. What is cgroup?
22 2-1. Mounting
23 2-2. Organizing Processes and Threads
24 2-2-1. Processes
25 2-2-2. Threads
26 2-3. [Un]populated Notification
[all …]
/Documentation/admin-guide/sysctl/
Dkernel.rst5 .. See scripts/check-sysctl-docs to keep this up to date
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
39 If BSD-style process accounting is enabled these values control
71 The machine hardware name, the same output as ``uname -m``
129 Ctrl-Alt-Delete). Writing a value to this file which doesn't
130 correspond to a running process will result in ``-ESRCH``.
132 See also `ctrl-alt-del`_.
236 ctrl-alt-del
239 When the value in this file is 0, ctrl-alt-del is trapped and
[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/process/
Dhandling-regressions.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
7 *We don't cause regressions* -- this document describes what this "first rule of
9 Documentation/admin-guide/reporting-regressions.rst, which covers the topic from a
21 loop by immediately sending at least a brief "Reply-all" with the list
30 introduced: v5.13..v5.14-rc1``. If not, send a reply (with the regressions
39 #regzbot introduced: v5.13..v5.14-rc1
45 mandated by Documentation/process/submitting-patches.rst and
61 -----------------------------------
72 it into the loop by sending at least a brief "Reply-all" with the list CCed;
79 Documentation/admin-guide/reporting-issues.rst.
[all …]
/Documentation/translations/sp_SP/
Dmemory-barriers.txt2 This is a version of Documentation/memory-barriers.txt translated into
35 consistencia de memoria formal y documentación en tools/memory-model/. Sin
53 Tenga en cuenta también que es posible que una barrera no valga (sea no-op)
63 - Operaciones del dispositivo.
64 - Garantías.
68 - Variedades de barrera de memoria.
69 - ¿Qué no se puede asumir sobre las barreras de memoria?
70 - Barreras de dirección-dependencia (históricas).
71 - Dependencias de control.
72 - Emparejamiento de barreras smp.
[all …]