Home
last modified time | relevance | path

Searched +full:self +full:- +full:describing (Results 1 – 19 of 19) sorted by relevance

/Documentation/filesystems/
Dxfs-self-describing-metadata.txt1 XFS Self Describing Metadata
2 ----------------------------
5 ------------
36 Self Describing Metadata
37 ------------------------
57 self describing metadata.
59 The first, fundamental requirement of self describing metadata is that the
66 Luckily, almost all XFS metadata has magic numbers embedded already - only the
68 magic numbers. Hence we can change the on-disk format of all these objects to
71 the metadata isn't self identifying. If it contains a new magic number, it is
[all …]
Dxfs-delayed-logging-design.txt2 --------------------------
4 Introduction to Re-logging in XFS
5 ---------------------------------
9 logged are made up of the changes to in-core structures rather than on-disk
10 structures. Other objects - typically buffers - have their physical changes
21 "re-logging". Conceptually, this is quite simple - all it requires is that any
45 (increasing) LSN of each subsequent transaction - the LSN is effectively a
48 This relogging is also used to implement long-running, multiple-commit
62 the log - repeated operations to the same objects write the same changes to
71 doing aggregation of transactions in memory - batching them, if you like - to
[all …]
/Documentation/devicetree/bindings/display/panel/
Dtpo,tpg110.yaml1 # 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/devicetree/bindings/arm/bcm/
Dbrcm,brcmstb.txt2 -----------------------------------------------
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/powerpc/
Dcxl.rst28 +----------+ +---------+
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
156 https://github.com/ibm-capi/libcxl
[all …]
/Documentation/process/
Dhowto.rst6 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 …]
Dadding-syscalls.rst9 :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/
Dlibsas.txt2 ---------
42 struct sas_phy --------------------
66 enabled -- must be set (0/1)
67 id -- must be set [0,MAX_PHYS)
68 class, proto, type, role, oob_mode, linkrate -- must be set
69 oob_mode -- you set this when OOB has finished and then notify
72 sas_addr -- this normally points to an array holding the sas
76 attached_sas_addr -- set this when you (LLDD) receive an
85 frame_rcvd -- this is where you copy the IDENTIFY/FIS frame
93 sas_prim -- this is where primitives go when they're
[all …]
/Documentation/livepatch/
Dlivepatch.rst15 5. Livepatch life-cycle
43 - The kernel probes are the most generic. The code can be redirected by
46 - The function tracer calls the code from a predefined location that is
48 compiler using the '-pg' gcc option.
50 - Livepatching typically needs to redirect the code at the very beginning
73 Most of these changes are self contained and the function presents itself
87 The aim is to define a so-called consistency model. It attempts to define
92 kpatch: it uses kGraft's per-task consistency and syscall barrier
96 Patches are applied on a per-task basis, when the task is deemed safe to
121 a) Patching I/O-bound user tasks which are sleeping on an affected
[all …]
/Documentation/media/uapi/
Dfdl-appendix.rst4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
17 .. _fdl-preamble:
44 .. _fdl-section1:
50 .. _fdl-document:
59 .. _fdl-modified:
66 .. _fdl-secondary:
68 A “Secondary Section” is a named appendix or a front-matter section of
[all …]
/Documentation/
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 …]
DIPMI.txt12 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 …]
/Documentation/driver-api/usb/
Dwriting_musb_glue_layer.rst15 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/
Dcgroups.rst6 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
84 ----------------------------
87 Linux kernel, mainly for resource-tracking purposes. Such efforts
101 different subsystems - having parallel hierarchies allows each
[all …]
Dcpusets.rst9 - Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
10 - Modified by Paul Jackson <pj@sgi.com>
11 - Modified by Christoph Lameter <cl@linux.com>
12 - Modified by Paul Menage <menage@google.com>
13 - Modified by Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
39 ----------------------
43 an on-line node that contains memory.
52 Documentation/admin-guide/cgroup-v1/cgroups.rst.
71 ----------------------------
75 non-uniform access times (NUMA) presents additional challenges for
[all …]
/Documentation/admin-guide/
Dras.rst33 -------------
47 Self-Monitoring, Analysis and Reporting Technology (SMART).
55 ---------------
68 * **Correctable Error (CE)** - the error detection mechanism detected and
72 * **Uncorrected Error (UE)** - the amount of errors happened above the error
73 correction threshold, and the system was unable to auto-correct.
75 * **Fatal Error** - when an UE error happens on a critical component of the
79 * **Non-fatal Error** - when an UE error happens on an unused component,
87 The mechanism for handling non-fatal errors is usually complex and may
92 ------------------------------------
[all …]
/Documentation/driver-api/
Dpinctl.rst9 - 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/down, open drain,
17 Top-level interface
22 - A pin controller is a piece of hardware, usually a set of registers, that
28 - PINS are equal to pads, fingers, balls or whatever packaging input or
32 be sparse - i.e. there may be gaps in the space with numbers where no
37 describing the pins handled by this specific pin controller.
98 See for example arch/arm/mach-u300/Kconfig for an example.
[all …]
/Documentation/security/keys/
Dcore.rst5 This service allows cryptographic keys, authentication tokens, cross-domain
30 - A serial number.
31 - A type.
32 - A description (for matching a key in a search).
33 - Access control information.
34 - An expiry time.
35 - A payload.
36 - State.
40 the lifetime of that key. All serial numbers are positive non-zero 32-bit
69 the keyring links; in the case of a user-defined key, it's an arbitrary
[all …]
/Documentation/networking/
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 …]