Searched full:record (Results 1 – 25 of 178) sorted by relevance
12345678
| /Documentation/driver-api/pldmfw/ |
| D | driver-ops.rst | 14 record matches the device being updated. This requires comparing the record
15 descriptors in the record with information from the device. Many record
19 The ``.match_record`` operation should return true if a given record matches
26 package data in a record to the device firmware. If the matching record
36 that is, for each component indicated by the matching record. The
|
| D | index.rst | 31 so, it sends the record and component data to the firmware using the device
42 Due to this, it is not straight forward to index the record, record
60 1. Parse the firmware file for record and component information
61 2. Scan through the records and determine if the device matches any record
62 in the file. The first matched record will be used.
63 3. If the matching record provides package data, send this package data to
65 4. For each component that the record indicates, send the component data to
|
| D | file-format.rst | 78 number of records in the file, followed by each record. A single device
79 record describes what device matches this record. All valid PLDM firmware
80 files must contain at least one record, but optionally may contain more than
81 one record if they support multiple devices.
83 Each record will identify the device it supports via TLVs that describe the
86 only subset of provided components will be used by a given record. A record
90 The following diagram provides an overview of the device record area::
95 | Record Count |
99 | Record 1 |
103 | Record 2 |
[all …]
|
| /Documentation/networking/ |
| D | tls-offload.rst | 33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
42 intercepts them, inserts record framing, performs encryption (in ``TLS_SW``
60 If device decrypted all the segments of the record the decryption is skipped,
100 as well as TLS record sequence number. ``start_offload_tcp_sn`` indicates
101 which TCP sequence number corresponds to the beginning of the record with
116 the expected sequence number and will have kernel record information.
134 * record metadata (sequence number, processing offset and length)
137 There are no guarantees on record length or record segmentation. In particular
138 segments may start at any point of a record and contain any number of records.
149 Record reassembly is not necessary for TLS offload. If the packets arrive
[all …]
|
| D | tls.rst | 69 For example, we can send an encrypted hello world record as follows:
89 MSG_MORE is passed. MSG_MORE will delay creation of a record until
90 MSG_MORE is not passed, or the maximum record size is reached.
103 are decrypted using TLS parameters provided. A full TLS record must
127 messages (record type 21) and handshake messages (record type 22), etc.
128 These messages can be sent over the socket by providing the TLS record type
130 using a record of type @record_type.
206 At a high level, the kernel TLS ULP is a replacement for the record
209 A patchset to OpenSSL to use ktls as the record layer is
214 Since it doesn't implement a full record layer, control
[all …]
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 94 record.
97 because record has to be prepared in some other place first. But it allows to
108 outside its reserved record space. bpf_ringbuf_output(), while slightly slower
113 a record as discarded, and such records are supposed to be ignored by consumer
115 all-or-nothing multi-record submission, or emulating temporary
118 Each reserved record is tracked by verifier through existing
120 impossible to reserve a record, but forget to submit (or discard) it.
150 same ring buffer, they will both get a record reserved (provided there is
164 Each time a record is reserved, producer that "owns" the record will
166 ready to be consumed, though. Each record has 8 byte header, which contains the
[all …]
|
| D | redirect.rst | 67 perf record
73 perf record -a -e xdp:xdp_redirect_err \
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 41 [ Generic Error Record (Mandatory) ]
42 [ FID record (Mandatory) ]
49 Generic error record
52 The generic error record provides enough information for a file system
54 providing any additional details about the problem. This record is
71 FID record
74 The FID record can be used to uniquely identify the inode that triggered
|
| D | ramoops.rst | 51 The module uses a counter to record multiple dumps but the counter gets reset
85 record-size = <0x4000>;
152 files is ``dmesg-ramoops-N``, where N is the record number in memory. To delete
153 a stored record from RAM, simply unlink the respective pstore file.
|
| /Documentation/ABI/testing/ |
| D | dev-kmsg | 26 Every read() from the opened device node receives one record
34 Every read() will receive the next available record. If no more
38 Messages in the record ring buffer get overwritten as whole,
43 and the seek position be updated to the next available record.
46 Unlike the classic syslog() interface, the 64 bit record
59 seek after the last record available at the time
|
| D | sysfs-bus-iio-accel-adxl372 | 6 which sets the device in a mode in which it will record only the peak acceleration
|
| /Documentation/dev-tools/ |
| D | autofdo.rst | 126 $ perf record -e BR_INST_RETIRED.NEAR_TAKEN:k -a -N -b -c <count> -o <perf_file> -- <loadtest>
142 …$ perf record --pfm-events RETIRED_TAKEN_BRANCH_INSTRUCTIONS:k -a -N -b -c <count> -o <perf_file> …
148 to record ETM traces for AutoFDO::
150 $ perf record -e cs_etm/@tmc_etr0/k -a -o <etm_perf_file> -- <loadtest>
156 to record ETM traces for AutoFDO::
158 $ simpleperf record -e cs-etm:k -a -o <perf_file> -- <loadtest>
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 84 record consists of this block name paired with the presumed location of
106 reading. The records are written to a series of record pages based on the
110 record page contains any given name. This index means that a request for a
111 name can determine exactly which record page may contain that record,
115 there is a record for this name, it will be on the indicated page. Closed
121 time a request finds a matching record in the index, that record is copied
127 mapping each block name to the chapter containing its newest record. This
129 ensuring that only the newest record for a given block name can be found.
130 An older record for a block name will no longer be found even though it has
133 say that a record exists for a name. It can only say which chapter would
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 23 At least one of "record-size", "console-size", "ftrace-size", or "pmsg-size"
44 record-size:
118 - required: [record-size]
140 record-size = <0x400>; /* 1kB */
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 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
92 Some others will actually use perf record and some test binaries that
102 These perf record tests will not run if the tool binaries do not exist
|
| /Documentation/arch/arm64/ |
| D | sme.rst | 120 * A new signal frame record TPIDR2_MAGIC is added formatted as a struct
123 * A new signal frame record za_context encodes the ZA register contents on
126 * The signal frame record for ZA always contains basic metadata, in particular
129 * The ZA matrix may or may not be included in the record, depending on
134 * If matrix data is present, the remainder of the record has a vl-dependent
142 space is allocated on the stack, an extra_context record is written in
146 * If ZTn is supported and PSTATE.ZA==1 then a signal frame record for ZTn will
149 * The signal record for ZTn has magic ZT_MAGIC (0x5a544e01) and consists of a
160 * If there is no za_context record in the signal frame, or if the record is
172 signal frame record for ZTn, resulting in a forced SIGSEGV.
|
| D | sve.rst | 133 * A new signal frame record sve_context encodes the SVE registers on signal
136 * This record is supplementary to fpsimd_context. The FPSR and FPCR registers
140 * The record contains a flag field which includes a flag SVE_SIG_FLAG_SM which
145 * The signal frame record for SVE always contains basic metadata, in particular
148 * The SVE registers may or may not be included in the record, depending on
153 * If the registers are present, the remainder of the record has a vl-dependent
162 space is allocated on the stack, an extra_context record is written in
172 * If there is no sve_context record in the signal frame, or if the record is
|
| /Documentation/arch/s390/ |
| D | monreader.rst | 139 contains information on the type of the following record set (sample/event
141 of the record set in the monitor DCSS. The start and end address can be used
142 to determine the size of the record set, the end address is the address of the
144 correctly (domain 1, record 13), i.e. it can be used to determine the record
163 There may be more than one combination of MCE and corresponding record set
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 15 CommTrouble [ shape=record,
48 …cluster_resync [ shape=record,label="{<any>resynchronisation process running\l'concurrent' applica…
|
| /Documentation/filesystems/ |
| D | qnx6.rst | 114 Eeach filename record additionally got a filename length field.
119 record plus the longfile inode number also stored in that record.
133 no block pointers and the directory file record pointing to the target file
|
| /Documentation/arch/powerpc/ |
| D | imc.rst | 163 To record an application/process with trace-imc event:
167 # perf record -e trace_imc/trace_cycles/ yes > /dev/null
168 [ perf record: Woken up 1 times to write data ]
169 [ perf record: Captured and wrote 0.012 MB perf.data (21 samples) ]
|
| /Documentation/core-api/ |
| D | watch_queue.rst | 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.
276 notification record. The notification is only written into the buffer if::
|
| /Documentation/devicetree/bindings/hwinfo/ |
| D | loongson,ls2k-chipid.yaml | 14 blocks, of which the ChipID group registers record SoC version,
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 165 transaction, we have to reserve enough space to record a full leaf-to-root split
534 Now that we can record transactional changes in memory in a form that allows
595 formatted log items and a commit record at the tail. From a recovery
606 the transaction commit record, but tracking this requires us to have a
683 attached to the log buffer that the commit record was written to along with a
713 To do this, transactions need to record the LSN of the commit record of the
739 the checkpoint context records the LSN of the commit record for the checkpoint,
740 we can also wait on the log buffer that contains the commit record, thereby
777 usage of the transaction. The reservation accounts for log record headers,
805 problematic. Typically log record headers use at least 16KB of log space per
[all …]
|
| D | xfs-online-fsck-design.rst | 382 The check function examines every record associated with the type for obvious
387 The repair function scans available metadata as needed to record all the
450 When the repair scanner needs to record an observation, the staging data are
485 Their method consists of an index builder that extracts relevant record data to
493 scan through the record space.
495 file updates are elided when the record ID for the update is greater than the
496 cursor position within the record ID space.
727 * For each record inside that metadata object...
729 * For each field inside that record...
937 ondisk block header to record a magic number, a checksum, a universally
[all …]
|
12345678