Home
last modified time | relevance | path

Searched +full:data +full:- +full:mirror (Results 1 – 25 of 25) sorted by relevance

/Documentation/vm/
Dhmm.rst7 Provide infrastructure and helpers to integrate non-conventional memory (device
23 CPU page-table mirroring works and the purpose of HMM in this context. The
52 For flat data sets (array, grid, image, ...) this isn't too hard to achieve but
53 for complex data sets (list, tree, ...) it's hard to get right. Duplicating a
54 complex data set needs to re-map all the pointer relations between each of its
56 duplicate data set and addresses.
58 Split address space also means that libraries cannot transparently use data
60 might have to duplicate its input data set using the device specific memory
71 are only do-able with a shared address space. It is also more reasonable to use
97 two-way cache coherency between CPU and device and allow all atomic operations the
[all …]
/Documentation/admin-guide/device-mapper/
Ddm-clone.rst1 .. SPDX-License-Identifier: GPL-2.0-only
4 dm-clone
10 dm-clone is a device mapper target which produces a one-to-one copy of an
11 existing, read-only source device into a writable destination device: It
12 presents a virtual block device which makes all data appear immediately, and
15 The main use case of dm-clone is to clone a potentially remote, high-latency,
16 read-only, archival-type block device into a writable, fast, primary-type device
17 for fast, low-latency I/O. The cloned device is visible/mountable immediately
21 For example, one could restore an application backup from a read-only copy,
26 When the cloning completes, the dm-clone table can be removed altogether and be
[all …]
Dkcopyd.rst5 Kcopyd provides the ability to copy a range of sectors from one block-device
6 to one or more other block-devices, with an asynchronous completion
7 notification. It is used by dm-snapshot and dm-mirror.
18 block-device along with the starting sector and size of the region. The source
30 completion callback routine, and a pointer to some context data for the copy::
Ddm-init.rst5 It is possible to configure a device-mapper device to act as the root device for
11 The second is to create one or more device-mappers using the module parameter
12 "dm-mod.create=" through the kernel boot command line argument.
14 The format is specified as a string of data separated by commas and optionally
15 semi-colons, where:
17 - a comma is used to separate fields like name, uuid, flags and table
19 - a semi-colon is used to separate devices.
23 …dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<tab…
28 <uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
35 `--concise` argument.
[all …]
Dcache.rst8 dm-cache is a device mapper target written by Joe Thornber, Heinz
12 dynamically migrating some of its data to a faster, smaller device
15 This device-mapper solution allows us to insert this caching at
16 different levels of the dm stack, for instance above the data device for
17 a thin-provisioning pool. Caching solutions that are integrated more
20 The target reuses the metadata library used in the thin-provisioning
23 The decision as to what data to migrate and when is left to a plug-in
46 Sub-devices
47 -----------
52 1. An origin device - the big, slow one.
[all …]
Ddm-raid.rst2 dm-raid
5 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
6 It allows the MD RAID drivers to be accessed using a device-mapper
11 -----------------------
26 - Transitory layout
29 - rotating parity 0 with data continuation
32 - rotating parity N with data continuation
35 - rotating parity 0 with data restart
38 - rotating parity N with data restart
41 - rotating parity zero (left-to-right) with data restart
[all …]
/Documentation/m68k/
Dbuddha-driver.rst8 ------------------------------------------------------------------------
11 Buddha-part of the Catweasel Zorro-II version
21 product number: 0 (42 for Catweasel Z-II)
23 Rom-vector: $1000
25 The card should be a Z-II board, size 64K, not for freemem
26 list, Rom-Vektor is valid, no second Autoconfig-board on the
30 as the Amiga Kickstart does: The lower nibble of the 8-Bit
36 otherwise your chance is only 1:16 to find the board :-).
38 The local memory-map is even active when mapped to $e8:
41 $0-$7e Autokonfig-space, see Z-II docs.
[all …]
/Documentation/filesystems/
Dfiemap.txt6 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
11 --------------
30 which the process would like mappings for. Extents returned mirror
31 those on disk - that is, the logical offset of the 1st returned extent
59 extended attribute lookup tree, instead of its data tree.
63 --------------
91 All offsets and lengths are in bytes and mirror those on disk. It is valid
110 for inline or tail-packed data can key on the specific flag. Software
111 which simply cares not to try operating on non-aligned extents
114 data. Note that the opposite is not true - it would be valid for
[all …]
Dntfs.txt8 - Overview
9 - Web site
10 - Features
11 - Supported mount options
12 - Known bugs and (mis-)features
13 - Using NTFS volume and stripe sets
14 - The Device-Mapper driver
15 - The Software RAID / MD driver
16 - Limitations when using the MD driver
22 Linux-NTFS comes with a number of user-space programs known as ntfsprogs.
[all …]
Dubifs-authentication.rst13 is a lost smartphone where the attacker is unable to read personal data stored
20 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
24 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
27 time. For dm-crypt and other filesystems that build upon the Linux block IO
28 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
29 can be used to get full data authentication at the block layer.
30 These can also be combined with dm-crypt [CRYPTSETUP2].
40 ----------------
46 addition, it deals with flash-specific wear-leveling and transparent I/O error
56 +------------+ +*******+ +-----------+ +-----+
[all …]
/Documentation/devicetree/bindings/display/panel/
Dlvds.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 LVDS is a physical layer specification defined in ANSI/TIA/EIA-644-A. Multiple
15 incompatible data link layers have been used over time to transmit image data
19 [JEIDA] "Digital Interface Standards for Monitor", JEIDA-59-1999, February
27 FPD-Link and FlatLink brands.
30 - $ref: panel-common.yaml#
[all …]
/Documentation/arm/omap/
Ddss.rst7 TV-out and multiple display support, but there are lots of small improvements
10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
15 --------
19 - MIPI DPI (parallel) output
20 - MIPI DSI output in command mode
21 - MIPI DBI (RFBI) output
22 - SDI output
23 - TV output
24 - All pieces can be compiled as a module or inside kernel
25 - Use DISPC to update any of the outputs
[all …]
/Documentation/firmware-guide/acpi/apei/
Doutput_format.rst1 .. SPDX-License-Identifier: GPL-2.0
19 <section data>
30 <section data> :=
31 <generic processor section data> | <memory section data> | \
32 <pcie section data> | <null>
34 <generic processor section data> :=
55 [cache error][, TLB error][, bus error][, micro-architectural error]
57 <proc operation string>* := unknown or generic | data read | data write | \
63 <memory section data> :=
81 unknown | no error | single-bit ECC | multi-bit ECC | \
[all …]
/Documentation/w1/
Dw1-netlink.rst21 [struct cn_msg] - connector header.
22 Its length field is equal to size of the attached data
23 [struct w1_netlink_msg] - w1 netlink header.
24 __u8 type - message type.
37 __u8 status - error indication from kernel
38 __u16 len - size of data attached to this header data
40 __u8 id[8]; - slave unique device id
42 __u32 id; - master's id
43 __u32 res; - reserved
47 [struct w1_netlink_cmd] - command for given master or slave device.
[all …]
/Documentation/input/
Dgameport-programming.rst28 space (is above 0x1000), use that one, and don't map the ISA mirror.
34 Please also consider enabling the gameport on the card in the ->open()
35 callback if the io is mapped to ISA space - this way it'll occupy the io
37 ->close() callback. You also can select the io address in the ->open()
70 the driver doesn't have to measure them the old way - an ADC is built into
86 return -(mode != GAMEPORT_MODE_COOKED);
95 experimentation, it is the amount of noise in the ADC data. Perfect
97 See analog.c and input.c for handling of fuzz - the fuzz value determines
99 in the data.
105 examples 1+2 or 1+3. Gameports can support internal calibration - see below,
[all …]
/Documentation/media/v4l-drivers/
Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
13 data from LCD controller (FIMD) through the SoC internal writeback data
17 drivers/media/platform/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, EXYNOS4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
[all …]
/Documentation/media/uapi/v4l/
Dcontrol.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
16 Devices typically have a number of user-settable controls such as
28 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
29 :ref:`control-id`. The ID is used when querying the attributes of a
34 the user is supposed to understand. When the purpose is non-intuitive
35 the driver writer should provide a user manual, a user interface plug-in
64 .. _control-id:
[all …]
/Documentation/filesystems/caching/
Dfscache.txt12 FS-Cache mediates between cache backends (such as CacheFS) and network
15 +---------+
16 | | +--------------+
17 | NFS |--+ | |
18 | | | +-->| CacheFS |
19 +---------+ | +----------+ | | /dev/hda5 |
20 | | | | +--------------+
21 +---------+ +-->| | |
22 | | | |--+
23 | AFS |----->| FS-Cache |
[all …]
Dnetfs-api.txt2 FS-CACHE NETWORK FILESYSTEM API
5 There's an API by which a network filesystem can make use of the FS-Cache
10 FS-Cache to make finding objects faster and to make retiring of groups of
17 (3) Barring the top-level index (one entry per cached netfs), the index
30 (7) Data file registration
32 (9) Setting the data file size
35 (12) Index and data file consistency
40 (17) Data file invalidation
41 (18) FS-Cache specific page flags.
48 FS-Cache needs a description of the network filesystem. This is specified
[all …]
/Documentation/driver-api/
Dmtdnand.rst10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
86 - [BOARDSPECIFIC]
[all …]
/Documentation/admin-guide/
Dras.rst33 -------------
39 it causes data loss or system downtime.
45 * I/O – add CRC checksums for transferred data;
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
77 only reliable way to avoid data corruption is to hang or reboot the machine.
[all …]
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 …]
Ddevices.txt1 0 Unnamed devices (e.g. non-device mounts)
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
44 These are the old-style (BSD) PTY devices; Unix98
106 3 char Pseudo-TTY slaves
112 These are the old-style (BSD) PTY devices; Unix98
115 3 block First MFM, RLL and IDE hard disk/CD-ROM interface
[all …]
/Documentation/scsi/
Dncr53c8xx.txt5 95170 DEUIL LA BARRE - FRANCE
57 10.4 PCI configuration fix-up boot option
68 14.4 Possible data corruption during a Memory Write and Invalidate
74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
94 Stefan Esser <se@mi.Uni-Koeln.de>
98 - ncr53c8xx generic driver that supports all the SYM53C8XX family including
101 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest
107 PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
118 Useful SCSI tools written by Eric Youngdale are available at tsx-11:
[all …]
/Documentation/virt/uml/
DUserModeLinux-HOWTO.txt130 15.3 Buglets and clean-ups
151 +-----------+-----------+----+
153 +-----------+-----------+----+
155 +----------------------------+
157 +----------------------------+
165 User-Mode Linux as if they were running under a normal kernel, like
170 +----------------+
172 +-----------+----------------+
173 | Process 1 | User-Mode Linux|
174 +----------------------------+
[all …]