Searched +full:record +full:- +full:size (Results 1 – 25 of 96) sorted by relevance
1234
| /Documentation/driver-api/pldmfw/ |
| D | file-format.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
15 +----------------------+
19 +----------------------+
23 +----------------------+
27 +----------------------+
31 +----------------------+
35 +----------------------+
39 +----------------------+
43 +----------------------+
47 +----------------------+
[all …]
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 12 ----------
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
56 The approach chosen has an advantage of re-using existing BPF map
62 combined with ``ARRAY_OF_MAPS`` and ``HASH_OF_MAPS`` map-in-maps to implement
70 the size of ring buffer and has to be a power of 2 value.
75 - variable-length records;
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 recovered after a reboot. This is a child-node of "/reserved-memory", and
16 as kernel log messages, or for optional ECC error-correction data. The total
17 size of these optional buffers must fit in the reserved region.
20 records. These records have a configurable size, with a size of 0 indicating
23 At least one of "record-size", "console-size", "ftrace-size", or "pmsg-size"
24 must be set non-zero, but are otherwise optional as listed below.
[all …]
|
| /Documentation/networking/ |
| D | tls-offload.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
13 For details regarding the user-facing interface refer to the TLS
18 * Software crypto mode (``TLS_SW``) - CPU handles the cryptography.
24 * Packet-based NIC offload mode (``TLS_HW``) - the NIC handles crypto
28 (``ethtool`` flags ``tls-hw-tx-offload`` and ``tls-hw-rx-offload``).
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
36 offload opt-in or opt-out on per-connection basis is not currently supported.
39 --
42 intercepts them, inserts record framing, performs encryption (in ``TLS_SW``
[all …]
|
| D | tls.rst | 11 TCP. TLS provides end-to-end data integrity and confidentiality.
17 -------------------------
21 .. code-block:: c
29 data-path to the kernel. There is a separate socket option for moving
32 .. code-block:: c
65 ----------------------------
69 For example, we can send an encrypted hello world record as follows:
71 .. code-block:: c
82 .. code-block:: c
89 MSG_MORE is passed. MSG_MORE will delay creation of a record until
[all …]
|
| /Documentation/arch/s390/ |
| D | monreader.rst | 5 Date : 2004-Nov-26
33 See also "CP Command and Utility Reference" (SC24-6081-00) for more information
35 and Administration" (SC24-6116-00) for more information on DCSSes.
38 -----------
44 This defines two blocks of storage, the first is 140MB in size an begins at
45 address 0MB, the second is 200MB in size and begins at address 200MB,
47 always start at 0 and be at least 64MB in size.
50 -----------
59 This defines 140MB storage size for your guest, the parameter "mem=160M" is
78 Refer to the "z/VM Performance" book (SC24-6109-00) on how to create a monitor
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 1 .. 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.
16 Because deduplication rates fall drastically as the block size increases, a
17 vdo target has a maximum block size of 4K. However, it can achieve
25 The design of dm-vdo is based on the idea that deduplication is a two-part
[all …]
|
| /Documentation/arch/arm64/ |
| D | sme.rst | 19 -----------
26 instructions and registers, and the Linux-specific system interfaces
31 the SME2 instructions and ZT0, and the Linux-specific system interfaces
58 cpu-feature-registers.txt for details.
69 vectors from 0 to VL/8-1 stored in the same endianness invariant format as is
76 ------------------
79 controls the size of the streaming mode SVE vectors and the ZA matrix array.
84 3. Sharing of streaming and non-streaming mode SVE state
85 ---------------------------------------------------------
88 between streaming and non-streaming modes. When switching between modes
[all …]
|
| D | sve.rst | 23 -----------
26 tracked per-thread.
34 instructions and registers, and the Linux-specific system interfaces
61 cpu-feature-registers.txt for details.
79 an endianness-invariant layout, with bits [(8 * i + 7) : (8 * i)] encoded at
84 Beware that on big-endian systems this results in a different byte order than
85 for the FPSIMD V-registers, which are stored as single host-endian 128-bit
86 values, with bits [(127 - 8 * i) : (120 - 8 * i)] of the register encoded at
91 -----------------------------
93 The size of an SVE vector (Z) register is referred to as the "vector length".
[all …]
|
| /Documentation/admin-guide/ |
| D | ramoops.rst | 9 ------------
17 ----------------
19 Ramoops uses a predefined memory area to store the dump. The start and size
23 * ``mem_size`` for the size. The memory size will be rounded down to a
51 The module uses a counter to record multiple dumps but the counter gets reset
60 ----------------------
68 the kernel to use only the first 128 MB of memory, and place ECC-protected
74 ``Documentation/devicetree/bindings/reserved-memory/ramoops.yaml``.
77 reserved-memory {
78 #address-cells = <2>;
[all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 CoreSight - Perf
13 can log such data with a perf record command like::
15 perf record -e cs_etm//u testbinary
17 This would run some test binary (testbinary) until it exits and record
22 perf report --stdio --dump -i perf.data
26 …0x1e78 [0x30]: PERF_RECORD_AUXTRACE size: 0x11dd0 offset: 0 ref: 0x1b614fc1061b0ad1 idx: 0 tid…
28 . ... CoreSight ETM Trace data: size 73168 bytes
48 for the support such as libopencsd and libopencsd-dev or download it
60 ------------------------
[all …]
|
| /Documentation/filesystems/ |
| D | qnx6.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 ------
32 size of 512, 1024, 2048 or 4096, which is decided when the filesystem is
39 ---------------
55 Each of these root nodes holds information like total size of the stored
65 Unused block pointers are always set to ~0 - regardless of root node,
71 The first Superblock is located at 0x2000. (0x2000 is the bootblock size)
79 0x1000 is the size reserved for each superblock - regardless of the
83 ------
90 size, number of blocks used, access time, change time and modification time.
[all …]
|
| D | ocfs2-online-filecheck.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 OCFS2 file system - online file check
11 OCFS2 is often used in high-availability systems. However, OCFS2 usually
12 converts the filesystem to read-only when encounters an error. This may not be
13 necessary, since turning the filesystem read-only would affect other running
16 -EIO errno to the calling process and terminate further processing so that the
18 read-only, and the problematic file's inode number is reported in the kernel
23 This effort is to check/fix small issues which may hinder day-to-day operations
24 of a cluster filesystem by turning the filesystem read-only. The scope of
54 inode, fixing inode and setting the size of result record history.
[all …]
|
| /Documentation/admin-guide/kdump/ |
| D | vmcoreinfo.rst | 9 information from the kernel like structure size, page size, symbol
11 section and used by user-space tools like crash and makedumpfile to
18 ------------------------
25 ---------
27 The size of a page. It is the smallest unit of data used by the memory
28 management facilities. It is usually 4096 bytes of size and a page is
32 -----------
39 User-space tools can get the kernel name, host name, kernel release
43 ---------------------
49 ---------------
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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
63 The type and size of reservation must be matched to the modification taking
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/soc/fsl/ |
| D | fsl,qman-fqd.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/fsl/fsl,qman-fqd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
14 for QMan Frame Queue Descriptor (FQD) and Packed Frame Descriptor Record (PFDR).
15 This memory is reserved/allocated as a node under the /reserved-memory node.
19 a node under the /reserved-memory node.
21 The QMan FQD memory node must be named "qman-fqd"
22 The QMan PFDR memory node must be named "qman-pfdr"
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | inodes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -----------
15 links and is in general more seek-happy than ext4 due to its simpler
22 ``(inode_number - 1) / sb.s_inodes_per_group``, and the offset into the
23 group's table is ``(inode_number - 1) % sb.s_inodes_per_group``. There
31 .. list-table::
33 :header-rows: 1
36 * - Offset
37 - Size
38 - Name
[all …]
|
| /Documentation/core-api/ |
| D | watch_queue.rst | 29 additions to the ring - which might end up interleaved with notification
62 "type" indicates the source of the notification record and "subtype" indicates
63 the type of record from that source (see the Watch Sources section below). The
64 type may also be "WATCH_TYPE_META". This is a special record type generated
77 the size of the record, which may be between 8 and 127 bytes.
84 * A type-specific field (WATCH_INFO_TYPE_INFO). This is set by the
100 non-global watch list is typically referred to by reference to the object it
160 The ``info_id`` value should be an 8-bit number obtained from userspace and
181 driver-settable fields in the watch struct must have been set before this
216 should be passed in. The notification may be larger than this and the size in
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | dw100.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 <--------------------------------------->
17 ^ .-------.-------.-------.-------.-------.
21 a | .-------.-------.-------.-------.-------.
25 h | .-------.-------.-------.-------.-------.
29 h | .-------.-------.-------.-------.-------.
33 v '-------'-------'-------'-------'-------'
38 Each x, y coordinate register uses 16 bits to record the coordinate address in
42 .----------------------.--------..----------------------.--------.
45 '----------------------'--------''----------------------'--------'
[all …]
|
| /Documentation/admin-guide/mm/damon/ |
| D | start.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 ------
25 ---------------
44 $ sudo damo start "./masim ./configs/stairs.cfg --quiet"
56 total size: 577.590 MiB
68 (``age XX``). For example, the fifth region of ~9 MiB size is being most
79 The commands below record the memory access patterns of a program and save the
83 $ sudo damo record -o damon.data $(pidof masim)
88 with your real workload. The last line asks ``damo`` to record the access
96 (x-axis) got accessed when (y-axis) and how frequently (number).::
[all …]
|
| /Documentation/ABI/testing/ |
| D | pstore | 15 # mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore
17 $ ls -l /sys/fs/pstore/
19 -r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
24 - "dmesg" - saved console log
25 - "mce" - architecture dependent data from fatal h/w error
29 device that it can reclaim the space for later re-use::
31 $ rm /sys/fs/pstore/dmesg-erst-1
40 multiple) files based on the record size of the underlying
|
| D | sysfs-class-cxl | 11 Contact: linuxppc-dev@lists.ozlabs.org
22 Contact: linuxppc-dev@lists.ozlabs.org
29 Users: https://github.com/ibm-capi/libcxl
33 Contact: linuxppc-dev@lists.ozlabs.org
39 Users: https://github.com/ibm-capi/libcxl
43 Contact: linuxppc-dev@lists.ozlabs.org
45 Decimal value of the size of the MMIO space that may be mmapped
47 Users: https://github.com/ibm-capi/libcxl
51 Contact: linuxppc-dev@lists.ozlabs.org
55 Users: https://github.com/ibm-capi/libcxl
[all …]
|
| /Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
94 -----------------
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | fixed-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 on-flash partition table such as RedBoot.
18 - Rafał Miłecki <rafal@milecki.pl>
23 - const: fixed-partitions
24 - items:
25 - const: sercomm,sc-partitions
26 - const: fixed-partitions
[all …]
|
1234