Searched +full:self +full:- +full:describing (Results 1 – 25 of 28) sorted by relevance
12
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 XFS Self Describing Metadata
40 Self Describing Metadata
61 self describing metadata.
63 The first, fundamental requirement of self describing metadata is that the
70 Luckily, almost all XFS metadata has magic numbers embedded already - only the
72 magic numbers. Hence we can change the on-disk format of all these objects to
75 the metadata isn't self identifying. If it contains a new magic number, it is
76 self identifying and we can do much more expansive automated verification of the
79 As a primary concern, self describing metadata needs some form of overall
[all …]
|
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 xfs-delayed-logging-design
12 xfs-maintainer-entry-profile
13 xfs-self-describing-metadata
14 xfs-online-fsck-design
|
| D | xfs-delayed-logging-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 We begin with an overview of transactions in XFS, followed by describing how
33 details logged are made up of the changes to in-core structures rather than
34 on-disk structures. Other objects - typically buffers - have their physical
64 place. This means that permanent transactions can be used for one-shot
65 modifications, but one-shot reservations cannot be used for permanent
68 In the code, a one-shot transaction pattern looks somewhat like this::
97 While this might look similar to a one-shot transaction, there is an important
123 the on-disk journal.
165 transaction, we have to reserve enough space to record a full leaf-to-root split
[all …]
|
| D | xfs-online-fsck-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
59 - Provide a hierarchy of names through which application programs can associate
62 - Virtualize physical storage media across those names, and
64 - Retrieve the named data blobs at any time.
66 - Examine resource usage.
79 cross-references different types of metadata records with each other to look
[all …]
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | tpo,tpg110.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Thierry Reding <thierry.reding@gmail.com>
20 self-describing.
22 +--------+
23 SPI -> | TPO | -> physical display
24 RGB -> | TPG110 |
25 +--------+
[all …]
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 ------------------
37 Like ``clang-format`` for the rest of the kernel, ``rustfmt`` works on
43 --------
51 .. code-block:: rust
60 .. code-block:: rust
73 .. code-block:: rust
84 pub fn f(x: i32) -> Foo {
92 .. code-block:: rust
106 ------------------
[all …]
|
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 2 -----------------------------------------------
3 Boards with Broadcom Brahma15 ARM-based BCMxxxx (generally BCM7xxx variants)
7 - compatible: "brcm,bcm<chip_id>", "brcm,brcmstb"
11 #address-cells = <2>;
12 #size-cells = <2>;
16 Further, syscon nodes that map platform-specific registers used for general
19 - compatible: "brcm,bcm<chip_id>-sun-top-ctrl", "syscon"
20 - compatible: "brcm,bcm<chip_id>-cpu-biu-ctrl",
21 "brcm,brcmstb-cpu-biu-ctrl",
23 - compatible: "brcm,bcm<chip_id>-hif-continuation", "syscon"
[all …]
|
| /Documentation/admin-guide/ |
| D | quickly-build-trimmed-linux.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 testing purposes, but perfectly fine for day-to-day use, too.
15 section below: it contains a step-by-step guide, which is more detailed, but
21 self-compiled Linux kernels; install compilers and everything else needed for
26 git clone --depth 1 -b master \
34 make -j $(nproc --all)
37 command -v installkernel && sudo make modules_install install
43 git fetch --depth 1 origin
45 git checkout --force --detach origin/master
49 make -j $(nproc --all)
[all …]
|
| D | verify-bugs-and-bisect-regressions.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 currently supported by developers -- to then explain how to locate the change
22 read and navigate this document -- especially when you want to look something
26 https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
33 the same commands as this section while describing them in brief fashion. The
45 *segment 2*. Then you can submit a preliminary report -- or continue with
47 full-fledged regression report. In the following example 6.0.13 is assumed to be
55 # * Ensure Secure Boot permits booting self-compiled Linux kernels.
59 git clone -o mainline --no-checkout \
[all …]
|
| /Documentation/arch/powerpc/ |
| D | cxl.rst | 28 +----------+ +---------+
34 +----------+ +---------+
36 | +------+ | PSL |
37 | | CAPP |<------>| |
38 +---+------+ PCIE +---------+
65 - POWER8 and PSL Version 8 are compliant to the CAIA Version 1.0.
66 - POWER9 and PSL Version 9 are compliant to the CAIA Version 2.0.
104 just a per context portion. The hardware is self describing, hence
123 The WED is a 64-bit parameter passed to the AFU when a context is
157 https://github.com/ibm-capi/libcxl
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 libbpf is a C-based library containing a BPF loader that takes compiled BPF
13 The following are the high-level features supported by libbpf:
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
17 functionality, which is useful when users need more fine-grained control
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
48 (setting BPF program types, if necessary; pre-setting initial values for
87 * ``<name>__attach()`` – attaches all auto-attachable BPF programs (it’s
[all …]
|
| /Documentation/process/ |
| D | howto.rst | 6 This is the be-all, end-all document on this topic. It contains
18 ------------
23 know to achieve this by describing the process you need to go through,
27 The kernel is written mostly in C, with some architecture-dependent
30 you plan to do low-level development for that architecture. Though they
34 - "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
35 - "Practical C Programming" by Steve Oualline [O'Reilly]
36 - "C: A Reference Manual" by Harbison and Steele [Prentice Hall]
60 ------------
65 described in :ref:`Documentation/process/license-rules.rst <kernel_licensing>`.
[all …]
|
| D | adding-syscalls.rst | 9 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`.
13 ------------------------
18 kernel, there are other possibilities -- choose what fits best for your
21 - If the operations involved can be made to look like a filesystem-like
26 - If the new functionality involves operations where the kernel notifies
30 - However, operations that don't map to
31 :manpage:`read(2)`/:manpage:`write(2)`-like operations
35 - If you're just exposing runtime system information, a new node in sysfs
41 - If the operation is specific to a particular file or file descriptor, then
47 - If the operation is specific to a particular task or process, then an
[all …]
|
| /Documentation/scsi/ |
| D | libsas.rst | 1 .. SPDX-License-Identifier: GPL-2.0
47 ------------------
75 - must be set (0/1)
78 - must be set [0,MAX_PHYS)]
81 - must be set
84 - you set this when OOB has finished and then notify
88 - this normally points to an array holding the sas
93 - set this when you (LLDD) receive an
103 - this is where you copy the IDENTIFY/FIS frame
112 - this is where primitives go when they're
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 30 - The kernel probes are the most generic. The code can be redirected by
33 - The function tracer calls the code from a predefined location that is
35 compiler using the '-pg' gcc option.
37 - Livepatching typically needs to redirect the code at the very beginning
60 Most of these changes are self contained and the function presents itself
74 The aim is to define a so-called consistency model. It attempts to define
79 kpatch: it uses kGraft's per-task consistency and syscall barrier
83 Patches are applied on a per-task basis, when the task is deemed safe to
108 a) Patching I/O-bound user tasks which are sleeping on an affected
111 b) Patching CPU-bound user tasks. If the task is highly CPU-bound
[all …]
|
| /Documentation/userspace-api/media/ |
| D | fdl-appendix.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 .. _fdl-preamble:
37 .. _fdl-section1:
43 .. _fdl-document:
52 .. _fdl-modified:
59 .. _fdl-secondary:
61 A "Secondary Section" is a named appendix or a front-matter section of
62 the :ref:`Document <fdl-document>` that deals exclusively with the
73 .. _fdl-invariant:
76 :ref:`Secondary Sections <fdl-secondary>` whose titles are designated,
[all …]
|
| /Documentation/core-api/ |
| D | dma-api-howto.rst | 10 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 …]
|
| D | workqueue.rst | 18 describing which function to execute is put on a queue. An
33 thread system-wide. A single MT wq needed to keep around the same
60 * Use per-CPU unified worker pools shared by all wq to provide
85 worker-pools.
87 The cmwq design differentiates between the user-facing workqueues that
89 which manages worker-pools and processes the queued work items.
91 There are two worker-pools, one for normal work items and the other
93 worker-pools to serve work items queued on unbound workqueues - the
98 Each per-CPU BH worker pool contains only one pseudo worker which represents
110 When a work item is queued to a workqueue, the target worker-pool is
[all …]
|
| /Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
46 ------------------------
47 | | <------- drivers/usb/gadget
48 | Linux USB Core Stack | <------- drivers/usb/host
49 | | <------- drivers/usb/core
50 ------------------------
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 6 Documentation/admin-guide/cgroup-v1/cpusets.rst
12 Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
42 ----------------------
56 schedules a resource or applies per-cgroup limits, but it may be
62 hierarchy, and a set of subsystems; each subsystem has system-specific
69 User-level code may create and destroy cgroups by name in an
79 access. For example, cpusets (see Documentation/admin-guide/cgroup-v1/cpusets.rst) allow
83 .. _cgroups-why-needed:
86 ----------------------------
89 Linux kernel, mainly for resource-tracking purposes. Such efforts
[all …]
|
| D | cpusets.rst | 11 - Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
12 - Modified by Paul Jackson <pj@sgi.com>
13 - Modified by Christoph Lameter <cl@linux.com>
14 - Modified by Paul Menage <menage@google.com>
15 - Modified by Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
41 ----------------------
45 an on-line node that contains memory.
54 Documentation/admin-guide/cgroup-v1/cgroups.rst.
73 ----------------------------
77 non-uniform access times (NUMA) presents additional challenges for
[all …]
|
| /Documentation/driver-api/ |
| D | ipmi.rst | 12 standardized database for field-replaceable units (FRUs) and a watchdog
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
50 these enabled and let the drivers auto-detect what is present.
53 can have ACPI tables describing them.
61 "The SMBus Driver" on how to hand-configure your system.
65 the kernel, then via a kernel command-line option you can have the
74 'IPMI Poweroff' to do this. The driver will auto-detect if the system
89 ------------
[all …]
|
| D | pin-control.rst | 9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up, pull-down, open drain,
17 Top-level interface
22 - A PIN CONTROLLER is a piece of hardware, usually a set of registers, that
26 - PINS are equal to pads, fingers, balls or whatever packaging input or
30 be sparse - i.e. there may be gaps in the space with numbers where no
35 describing the pins handled by this specific pin controller.
60 .. code-block:: c
[all …]
|
| /Documentation/admin-guide/RAS/ |
| D | main.rst | 1 .. SPDX-License-Identifier: GPL-2.0
37 -------------
51 Self-Monitoring, Analysis and Reporting Technology (SMART).
59 ---------------
72 * **Correctable Error (CE)** - the error detection mechanism detected and
76 * **Uncorrected Error (UE)** - the amount of errors happened above the error
77 correction threshold, and the system was unable to auto-correct.
79 * **Fatal Error** - when an UE error happens on a critical component of the
83 * **Non-fatal Error** - when an UE error happens on an unused component,
91 The mechanism for handling non-fatal errors is usually complex and may
[all …]
|
| /Documentation/networking/dsa/ |
| D | dsa.rst | 22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
61 - the "dsa" port(s) are just conduits between two or more switches, and as such
[all …]
|
12