Searched full:log (Results 1 – 25 of 305) sorted by relevance
12345678910>>...13
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 40 The reason for these differences is to keep the amount of log space and CPU time
46 The method used to log an item or chain modifications together isn't
57 XFS has two types of high level transactions, defined by the type of log space
141 a "log force" to flush the outstanding committed transactions to stable storage
146 tend to use log forces to ensure modifications are on stable storage only when
160 A transaction reservation provides a guarantee that there is physical log space
164 log in the worst case. This means that if we are modifying a btree in the
179 log has this much space available before the transaction is allowed to proceed
180 so that when we come to write the dirty metadata into the log we don't run out
181 of log space half way through the write.
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 2 dm-log-writes
5 This target takes 2 devices, one to pass all IO to normally, and one to log all
9 able to take arbitrary data from userspace to insert into the log. The data
10 that is in the WRITE requests is copied into the log to make the replay happen
13 Log Ordering
16 We log things in order of completion once we are sure the write is no longer in
19 the log in a way that correlates to what is on disk and not what is in cache,
24 the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only
31 The log would show the following:
52 which isn't quite what happened and wouldn't be caught during the log replay.
[all …]
|
| D | dm-log.rst | 16 dm_dirty_log_type in include/linux/dm-dirty-log.h). Various different
23 disk drivers/md/dm-log.c
24 core drivers/md/dm-log.c
25 userspace drivers/md/dm-log-userspace* include/linux/dm-log-userspace.h
28 The "disk" log type
30 This log implementation commits the log state to disk. This way, the
33 The "core" log type
35 This log implementation keeps the log state in memory. The log state
38 available for storing log state.
40 The "userspace" log type
[all …]
|
| D | index.rst | 20 dm-log
29 log-writes
|
| D | dm-ima.rst | 52 Then IMA ASCII measurement log has the following format:
84 | To support recording duplicate IMA events in the IMA log, the Kernel needs to be configured with
103 The IMA measurement log has the following format for 'dm_table_load':
156 Then IMA ASCII measurement log will have the following entry:
173 The IMA measurement log has the following format for 'dm_device_resume':
197 then IMA ASCII measurement log will have an entry with:
211 The IMA measurement log has the following format for 'dm_device_remove':
235 then IMA ASCII measurement log will have the following entry:
252 The IMA measurement log has the following format for 'dm_table_clear':
269 then IMA ASCII measurement log will have an entry with:
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-xfs | 1 What: /sys/fs/xfs/<disk>/log/log_head_lsn
6 The log sequence number (LSN) of the current head of the
7 log. The LSN is exported in "cycle:basic block" format.
10 What: /sys/fs/xfs/<disk>/log/log_tail_lsn
15 The log sequence number (LSN) of the current tail of the
16 log. The LSN is exported in "cycle:basic block" format.
18 What: /sys/fs/xfs/<disk>/log/reserve_grant_head_bytes
23 The current state of the log reserve grant head. It
24 represents the total log reservation of all currently
28 What: /sys/fs/xfs/<disk>/log/write_grant_head_bytes
[all …]
|
| D | sysfs-firmware-log | 1 What: /sys/firmware/log
5 The /sys/firmware/log is a binary file that represents a
6 read-only copy of the firmware's log if one is
|
| D | dev-kmsg | 10 Every write() to the opened device node places a log entry in
19 log priority and the facility number is set to LOG_USER (1). It
85 all non-printable characters and '\' itself in the log message
89 key/value pairs to the log message, which provide the machine
122 the log consumer performs concatenation, the end result
127 Users: dmesg(1), userspace kernel log consumers
|
| D | sysfs-firmware-gsmi | 14 is limited to handling the system event log and getting
49 whole of the system event log. Values written
51 ASCII) representing the fraction of the log to
|
| D | sysfs-class-mic | 145 access the card OS log buffer via debugfs. When read, this entry
147 OS log buffer can be read. This entry is written by the host
148 configuration daemon to set the log buffer address. The correct
149 log buffer address to be written can be found in the System.map
159 access the card OS log buffer via debugfs. When read, this entry
160 provides the kernel virtual address where the card OS log buffer
162 daemon to set the log buffer length address. The correct log
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 5 This directory exposes error log entries retrieved
8 Each error log is identified by a unique ID and will
11 Each log entry has a directory in /sys/firmware/opal/elog.
13 Log entries may be purged by the service processor
15 Linux if there is no room for more log entries.
17 In the event that Linux has retrieved the log entries
19 the service processor needs more room for log entries,
20 the only remaining copy of a log message may be in
26 The service processor may be able to store more log
31 The raw log format is a binary format. We currently
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 4 TPM Event Log
7 This document briefly describes what TPM log is and how it is handed
13 The preboot firmware maintains an event log that gets new entries every
26 are accompanied by a measurement log. While not trusted on their own,
27 the measurement log contains a richer set of information than do the PCR
29 measurement log."
31 UEFI event log
34 UEFI provided event log has a few somewhat weird quirks.
36 Before calling ExitBootServices() Linux EFI stub copies the event log to
48 concatenating two halves of the event log from the custom configuration table
|
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 23 that sector 0 is used to keep a log of the latest changes, both to indicate that
57 SECTOR0 is the first sector on the device, and is used to hold the log of
76 All backup operations are logged to the first sector. The log sector has the
79 | Magic | Count | Sequence | Log entry | Log entry | …
82 Magic is a magic number. Count is the number of log entries. Sequence is 0
83 initially. A log entry is
89 When SECTOR0 is full, the log sector is backed up and another empty log sector
90 created with sequence number one higher. The first entry in any log entry with
91 sequence > 0 therefore must be the log of the backing up of the previous log
98 log entry to be written.
|
| /Documentation/networking/ |
| D | netfilter-sysctl.rst | 14 By default, only init_net namespace can log packets into kernel log
15 with LOG target; this aims to prevent containers from flooding host
16 kernel log. If enabled, this target also works in other network
|
| D | nf_conntrack-sysctl.rst | 85 - 1 - log ICMP packets
86 - 6 - log TCP packets
87 - 17 - log UDP packets
88 - 33 - log DCCP packets
89 - 41 - log ICMPv6 packets
90 - 136 - log UDPLITE packets
91 - 255 - log packets of any protocol
93 Log invalid packets of a type specified by value.
|
| /Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 28 z = log(x)/log(y);
30 The result of log(x) (a double) will be calculated, returned in f0, then
31 moved to f4 to preserve it over the log(y) call. The division will be done
32 in extended precision, due to the stfe instruction used to save f4 in log(y).
|
| /Documentation/ABI/removed/ |
| D | sysfs-mce | 27 0 always panic on uncorrected errors, log corrected errors
28 1 panic or SIGBUS on uncorrected errors, log corrected errors
29 2 SIGBUS or log uncorrected errors, log corrected errors
30 3 never panic or SIGBUS, log all errors (for testing only)
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 81 is organized as a simple write log. The log consists of 'meta data' and 'data'
87 of log head.
89 The log implementation is pretty straightforward. The difficult part is the
92 parity to the log, writes the data and parity to RAID disks after the data and
93 parity is settled down in log and finally the IO is finished. Read just reads
96 In write-back mode, MD writes IO data to the log and reports IO completion. The
99 MD will calculate parity for the data and write parity into the log. After this
106 from the log. The sequence ID and checksum will help us detect corrupted meta
|
| D | raid5-ppl.rst | 2 Partial Parity Log
5 Partial Parity Log (PPL) is a feature available for RAID5 arrays. The issue
27 parity are dispatched to disks. PPL is a distributed log - it is stored on
|
| /Documentation/core-api/ |
| D | printk-basics.rst | 12 - printk() messages can specify a log level.
19 All printk() messages are printed to the kernel log buffer, which is a ring
27 where ``KERN_INFO`` is the log level (note that it's concatenated to the format
28 string, the log level is not a separate argument). The available log levels are:
55 The log level specifies the importance of a message. The kernel decides whether
57 on its log level and the current *console_loglevel* (a kernel variable). If the
58 message priority is higher (lower log level value) than the *console_loglevel*
61 If the log level is omitted, the message is printed with ``KERN_DEFAULT``
69 The result shows the *current*, *default*, *minimum* and *boot-time-default* log
85 logging. This family of macros embed the log level in the macro names. For
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-adap-g-log-addrs.rst | 121 - Flags. See :ref:`cec-log-addrs-flags` for a list of available flags.
132 - Logical address types. See :ref:`cec-log-addr-types` for
135 to :ref:`CEC_LOG_ADDR_TYPE_UNREGISTERED <CEC-LOG-ADDR-TYPE-UNREGISTERED>`).
155 .. _cec-log-addrs-flags:
162 * .. _`CEC-LOG-ADDRS-FL-ALLOW-UNREG-FALLBACK`:
170 * .. _`CEC-LOG-ADDRS-FL-ALLOW-RC-PASSTHRU`:
180 * .. _`CEC-LOG-ADDRS-FL-CDC-ONLY`:
261 .. _cec-log-addr-types:
268 * .. _`CEC-LOG-ADDR-TYPE-TV`:
273 * .. _`CEC-LOG-ADDR-TYPE-RECORD`:
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 15 Parts of this storage may be set aside for other persistent log buffers, such
16 as kernel log messages, or for optional ECC error-correction data. The total
51 description: size in bytes of log buffer reserved for kernel messages
56 description: size in bytes of log buffer reserved for function tracing and profiling
61 description: size in bytes of log buffer reserved for userspace messages
78 default: 2 # log oopses and panics
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 38 DbC has been designed to log early printk messages. One use for
74 # tail -f /var/log/kern.log
129 root@target: tail -f /var/log/kern.log
142 root@host: tail -f /var/log/kern.log
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 65 DC (DCN) provides an extensive log that dumps multiple details from our
67 using Display Test Next (DTN) log, which can be captured via debugfs by using::
71 Since this log is updated accordingly with DCN status, you can also follow the
76 When reporting a bug related to DC, consider attaching this log before and
110 you can disable tracing and read the trace log by using the following::
117 attach the log that you obtain from the trace buffer in any bug reports that you
|
| /Documentation/devicetree/bindings/tpm/ |
| D | tpm-common.yaml | 25 base address of reserved memory allocated for firmware event log
30 size of reserved memory allocated for firmware event log
34 description: reserved memory allocated for firmware event log
|
12345678910>>...13