Home
last modified time | relevance | path

Searched +full:main +full:- +full:storage (Results 1 – 25 of 78) sorted by relevance

1234

/Documentation/firmware-guide/acpi/
Dchromeos-acpi-device.rst1 .. SPDX-License-Identifier: GPL-2.0
11 .. flat-table:: Supported ACPI Objects
13 :header-rows: 1
15 * - Object
16 - Description
18 * - CHSW
19 - Chrome OS switch positions
21 * - HWID
22 - Chrome OS hardware ID
24 * - FWID
[all …]
/Documentation/bpf/
Dmap_cgrp_storage.rst1 .. SPDX-License-Identifier: GPL-2.0-only
8 The ``BPF_MAP_TYPE_CGRP_STORAGE`` map type represents a local fix-sized
9 storage for cgroups. It is only available with ``CONFIG_CGROUPS``.
21 To access the storage in a program, use ``bpf_cgrp_storage_get``::
26 a new local storage will be created if one does not exist.
28 The local storage can be removed with ``bpf_cgrp_storage_delete``::
56 ptr = bpf_cgrp_storage_get(&cgrp_storage, task->cgroups->dfl_cgrp, 0,
81 The old cgroup storage map ``BPF_MAP_TYPE_CGROUP_STORAGE`` has been marked as
84 illusates the main difference between ``BPF_MAP_TYPE_CGRP_STORAGE`` and
91 (2). ``BPF_MAP_TYPE_CGRP_STORAGE`` supports local storage for more than one
[all …]
/Documentation/filesystems/
Dbtrfs.rst1 .. SPDX-License-Identifier: GPL-2.0
12 The main Btrfs features include:
14 * Extent based file storage (2^64 max file size)
24 * Scrub (on-line checksum verification)
Df2fs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 WHAT IS Flash-Friendly File System (F2FS)?
7 NAND flash memory-based storage devices, such as SSD, eMMC, and SD cards, have
10 disks, a file system, an upper layer to the storage device, should adapt to the
13 F2FS is a file system exploiting NAND flash memory-based storage devices, which
14 is based on Log-structured File System (LFS). The design has been focused on
18 Since a NAND flash memory-based storage device shows different characteristic
20 F2FS and its tools support various parameters not only for configuring on-disk
26 - git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git
30 - linux-f2fs-devel@lists.sourceforge.net
[all …]
/Documentation/ABI/testing/
Dsysfs-driver-chromeos-acpi18 Returns main firmware type for current boot (integer).
48 Returns physical memory address of the start of the main
56 Returns firmware version for the read-only portion of the
57 main processor firmware.
65 main processor firmware.
121 Returns the SHA-1 or SHA-256 hash that is read out of the
132 Returns offset in CMOS bank 0 of the verified boot non-volatile
133 storage block, counting from the first writable CMOS byte
142 Return the size in bytes of the verified boot non-volatile
143 storage block.
/Documentation/arch/riscv/
Dcmodx.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Concurrent Modification and Execution of Instructions (CMODX) for RISC-V Linux
8 modified by the program itself. Instruction storage and the instruction cache
9 (icache) are not guaranteed to be synchronized on RISC-V hardware. Therefore, the
16 storage with fence.i, the icache on the new hart will no longer be clean. This
19 instruction storage and icache.
23 userspace. The syscall performs a one-off icache flushing operation. The prctl
35 ---------------------
41 .. kernel-doc:: arch/riscv/mm/cacheflush.c
59 int main()
/Documentation/admin-guide/device-mapper/
Dvdo-design.rst1 .. SPDX-License-Identifier: GPL-2.0-only
4 Design of dm-vdo
7 The dm-vdo (virtual data optimizer) target provides inline deduplication,
8 compression, zero-block elimination, and thin provisioning. A dm-vdo target
9 can be backed by up to 256TB of storage, and can present a logical size of
12 production environments ever since. It was made open-source in 2017 after
14 dm-vdo. For usage, see vdo.rst in the same directory as this file.
19 reference a single 4K of actual storage. It can achieve compression rates
20 of 14:1. All zero blocks consume no storage at all.
25 The design of dm-vdo is based on the idea that deduplication is a two-part
[all …]
Dpersistent-data.rst8 The more-sophisticated device-mapper targets require complex metadata
12 - Mikulas Patocka's multisnap implementation
13 - Heinz Mauelshagen's thin provisioning target
14 - Another btree-based caching target posted to dm-devel
15 - Another multi-snapshot target based on a design of Daniel Phillips
20 The persistent-data library is an attempt to provide a re-usable
21 framework for people who want to store metadata in device-mapper
22 targets. It's currently used by the thin-provisioning target and an
23 upcoming hierarchical storage target.
28 The main documentation is in the header files which can all be found
[all …]
/Documentation/scsi/
Dufs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Universal Flash Storage
27 Universal Flash Storage (UFS) is a storage specification for flash devices.
28 It aims to provide a universal storage interface for both
29 embedded and removable flash memory-based storage in mobile
32 on the MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
35 The main goals of UFS are to provide:
41 - Support for Gear1 is mandatory (rate A: 1248Mbps, rate B: 1457.6Mbps)
42 - Support for Gear2 is optional (rate A: 2496Mbps, rate B: 2915.2Mbps)
46 - Gear3 (rate A: 4992Mbps, rate B: 5830.4Mbps)
[all …]
/Documentation/devicetree/bindings/mtd/
Dmarvell,nand-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/marvell,nand-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Miquel Raynal <miquel.raynal@bootlin.com>
15 - items:
16 - const: marvell,armada-8k-nand-controller
17 - const: marvell,armada370-nand-controller
18 - enum:
19 - marvell,ac5-nand-controller
[all …]
/Documentation/devicetree/bindings/mfd/
Dnxp,bbnsm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NXP Battery-Backed Non-Secure Module
10 - Jacky Bai <ping.bai@nxp.com>
13 NXP BBNSM serves as non-volatile logic and storage for the system.
16 main chip is power down. A time alarm is generated once the most
17 significant 32 bits of the real-time counter match the value in the
26 - enum:
27 - nxp,imx93-bbnsm
[all …]
/Documentation/devicetree/bindings/pmem/
Dpmem-region.txt1 Device-tree bindings for persistent memory regions
2 -----------------------------------------------------
6 a) Usable as main system memory (i.e. cacheable), and
10 storage device. To ensure data integrity the operating system needs to manage
16 -----------------------------
19 - compatible = "pmem-region"
21 - reg = <base, size>;
33 - Any relevant NUMA associativity properties for the target platform.
35 - volatile; This property indicates that this region is actually
36 backed by non-persistent memory. This lets the OS know that it
[all …]
/Documentation/devicetree/bindings/powerpc/nintendo/
Dgamecube.txt7 This node represents the multi-function "Flipper" chip, which packages
12 - compatible : Should be "nintendo,flipper"
21 - compatible : should be "nintendo,flipper-vi"
22 - reg : should contain the VI registers location and length
23 - interrupts : should contain the VI interrupt
27 Represents the data and control interface between the main processor
32 - compatible : should be "nintendo,flipper-pi"
33 - reg : should contain the PI registers location and length
43 - compatible : should be "nintendo,flipper-pic"
52 - compatible : should be "nintendo,flipper-dsp"
[all …]
Dwii.txt11 - model : Should be "nintendo,wii"
12 - compatible : Should be "nintendo,wii"
16 This node represents the multi-function "Hollywood" chip, which packages
21 - compatible : Should be "nintendo,hollywood"
30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
31 - reg : should contain the VI registers location and length
32 - interrupts : should contain the VI interrupt
36 Represents the data and control interface between the main processor
41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
42 - reg : should contain the PI registers location and length
[all …]
/Documentation/admin-guide/
Dinit.rst6 This document provides some high-level reasons for failure
14 partition), required drivers such as storage hardware (such as SCSI or
16 modules, to be pre-loaded by an initrd).
19 --> initial console unavailable. E.g. some serial consoles are unreliable
20 due to serial IRQ issues (e.g. missing interrupt-based configuration).
24 dependencies of the init binary such as ``/lib/ld-linux.so.2`` missing or
25 broken. Use ``readelf -d <INIT>|grep NEEDED`` to find out which libraries
30 hardware. In case you tried loading a non-binary file here (shell script?),
34 simple non-script binary such as ``/bin/sh`` and confirm its successful
35 execution. To find out more, add code ``to init/main.c`` to display
[all …]
/Documentation/block/
Dbfq-iosched.rst5 BFQ is a proportional-share I/O scheduler, with some extra
6 low-latency capabilities. In addition to cgroups support (blkio or io
7 controllers), BFQ's main features are:
9 - BFQ guarantees a high system and application responsiveness, and a
10 low latency for time-sensitive applications, such as audio or video
12 - BFQ distributes bandwidth, not just time, among processes or
18 schedules that may lead to a lower throughput. If your main or only
19 goal, for a given device, is to achieve the maximum-possible
20 throughput at all times, then do switch off all low-latency heuristics
25 As every I/O scheduler, BFQ adds some overhead to per-I/O-request
[all …]
/Documentation/security/keys/
Dtrusted-encrypted.rst26 * Root of trust for storage
30 Rooted to Storage Root Key (SRK) which never leaves the TPM that
31 provides crypto operation to establish root of trust for storage.
33 (2) TEE (Trusted Execution Environment: OP-TEE based on Arm TrustZone)
35 Rooted to Hardware Unique Key (HUK) which is generally burnt in on-chip
41 mode, trust is rooted to the OTPMK, a never-disclosed 256-bit key
45 (4) DCP (Data Co-Processor: crypto accelerator of various i.MX SoCs)
47 Rooted to a one-time programmable key (OTP) that is generally burnt
48 in the on-chip fuses and is accessible to the DCP encryption engine only.
72 The actual key sealing/unsealing is done on main processor/kernel space.
[all …]
/Documentation/translations/zh_CN/core-api/
Dsymbol-namespaces.rst1 .. include:: ../disclaimer-zh_CN.rst
3 :Original: Documentation/core-api/symbol-namespaces.rst
9 .. _cn_symbol-namespaces.rst:
21 --- 2.1 使用EXPORT_SYMBOL宏
22 --- 2.2 使用DEFAULT_SYMBOL_NAMESPACE定义
55 ``modpost`` 和kernel/module/main.c分别在构建时或模块加载时使用名称空间。
66 子系统的 ``Makefile`` 中定义默认命名空间。例如，如果要将usb-common中定义的所有符号导
69 ccflags-y += -DDEFAULT_SYMBOL_NAMESPACE='"USB_COMMON"'
96 $ modinfo drivers/usb/storage/ums-karma.ko
129 - 编写依赖未导入命名空间的符号的代码
[all …]
/Documentation/userspace-api/
Diommufd.rst1 .. SPDX-License-Identifier: GPL-2.0+
20 I/O page tables for all IOMMUs, with room in the design to add non-generic
31 --------------------
35 - IOMMUFD_OBJ_IOAS, representing an I/O address space (IOAS), allowing map/unmap
41 - IOMMUFD_OBJ_DEVICE, representing a device that is bound to iommufd by an
44 - IOMMUFD_OBJ_HW_PAGETABLE, representing an actual hardware I/O page table
50 All user-visible objects are destroyed via the IOMMU_DESTROY uAPI.
52 The diagram below shows relationship between user-visible objects and kernel
68 | | IOAS |<--| |<------| | |
81 | PFN storage | | | |
[all …]
Ddma-buf-alloc-exchange.rst1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright 2021-2023 Collabora Ltd.
9 support for sharing pixel-buffer allocations between processes, devices, and
12 approach this sharing for two-dimensional image data.
25 Conceptually a two-dimensional array of pixels. The pixels may be stored
30 A span along a single y-axis value, e.g. from co-ordinates (0,100) to
37 A span along a single x-axis value, e.g. from co-ordinates (100,0) to
46 A two-dimensional array of some or all of an image's color and alpha
80 A value that denotes the relationship between pixel-location co-ordinates
81 and byte-offset values. Typically used as the byte offset between two
[all …]
/Documentation/filesystems/spufs/
Dspu_run.rst1 .. SPDX-License-Identifier: GPL-2.0
10 spu_run - execute an spu context
25 Cell Broadband Engine Architecture in order to access Synergistic Pro-
26 cessor Units (SPUs). It uses the fd that was returned from spu_cre-
27 ate(2) to address a specific SPU context. When the context gets sched-
32 not return while the SPU is still running. If there is a need to exe-
33 cute SPU code in parallel with other code on either the main CPU or
42 gets filled when spu_run returns. It can be one of the following con-
52 A DMA storage error
59 spu_run returns the value of the spu_status register or -1 to indicate
[all …]
/Documentation/trace/
Dintel_th.rst1 .. SPDX-License-Identifier: GPL-2.0
8 --------
23 - Software Trace Hub (STH), trace source, which is a System Trace
25 - Memory Storage Unit (MSU), trace output, which allows storing
27 - Parallel Trace Interface output (PTI), trace output to an external
29 - Global Trace Hub (GTH), which is a switch and a central component
33 Documentation/ABI/testing/sysfs-bus-intel_th-output-devices, the most
39 description is at Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth.
54 [1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
57 ------------------
[all …]
/Documentation/usb/
Dehci.rst5 27-Dec-2002
8 USB 2.0-capable host controller hardware. The USB 2.0 standard is
11 - "High Speed" 480 Mbit/sec (60 MByte/sec)
12 - "Full Speed" 12 Mbit/sec (1.5 MByte/sec)
13 - "Low Speed" 1.5 Mbit/sec
31 While usb-storage devices have been available since mid-2001 (working
34 appear to be on hold until more systems come with USB 2.0 built-in.
39 other changes to the Linux-USB core APIs, including the hub driver,
43 - David Brownell
56 --------------
[all …]
/Documentation/admin-guide/mm/
Dconcepts.rst7 systems from MMU-less microcontrollers to supercomputers. The memory
80 improves TLB hit-rate and thus improves overall system performance.
87 Documentation/admin-guide/mm/hugetlbpage.rst.
94 name. See Documentation/admin-guide/mm/transhuge.rst for more details
118 Many multi-processor machines are NUMA - Non-Uniform Memory Access -
126 Documentation/admin-guide/mm/numa_memory_policy.rst.
136 storage device. The written pages are marked as `dirty` and when Linux
173 reclaimed. For instance, in-memory caches of filesystem metadata can
174 be re-read from the storage device and therefore it is possible to
175 discard them from the main memory when system is under memory
[all …]
/Documentation/devicetree/bindings/mailbox/
Dti,omap-mailbox.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
17 for message storage and interrupt configuration registers.
35 lines can also be routed to different processor sub-systems on DRA7xx as they
38 combine multiple clusters into a single IP block present within the Main
49 within a SoC. The sub-mailboxes (actual communication channels) are
56 "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
[all …]

1234