Home
last modified time | relevance | path

Searched refs:checkpoint (Results 1 – 18 of 18) sorted by relevance

/Linux-v5.4/Documentation/filesystems/
Dxfs-delayed-logging-design.txt302 size of a checkpoint to be slightly less than a half the log.
304 Apart from this size requirement, a checkpoint transaction looks no different
307 perspective, the checkpoint transaction is also no different - just a lot
311 Because the checkpoint is just another transaction and all the changes to log
314 minimise the time we hold the CIL locked while writing the checkpoint
318 per-checkpoint context that travels through the log write process through to
319 checkpoint completion.
321 Hence a checkpoint has a context that tracks the state of the current
322 checkpoint from initiation to checkpoint completion. A new context is initiated
323 at the same time a checkpoint transaction is started. That is, when we remove
[all …]
Dnilfs2.txt57 cp=n Specify the checkpoint-number of the snapshot to be
64 checkpoint if no metadata update is going. This mode
93 NILFS_IOCTL_CHANGE_CPMODE Change mode of given checkpoint between
94 checkpoint and snapshot state. This ioctl is
97 NILFS_IOCTL_DELETE_CHECKPOINT Remove checkpoint from NILFS2 file system.
136 NILFS_IOCTL_SYNC Make a checkpoint. This ioctl is used in
161 mkcp make a checkpoint or a snapshot.
162 chcp change an existing checkpoint to a snapshot or vice versa.
163 rmcp invalidate specified checkpoint(s).
169 where <cno> is the checkpoint number of the snapshot.
[all …]
Df2fs.txt49 the upper index structures such as inode, inode map, and checkpoint block are
158 data_flush Enable data flushing before checkpoint in order to
222 checkpoint=%s[:%u[%]] Set to "disable" to turn off checkpointing. Set to "enable"
227 While mounting with checkpoint=disabled, the filesystem must
234 with checkpoint=disable:100% would always succeed, but it may
237 This space is reclaimed once checkpoint=enable.
296 volume size, f2fs tries to conduct checkpoint to
303 checkpoint is triggered, and issued during the
304 checkpoint. By default, it is disabled with 0.
373 cp_interval F2FS tries to do checkpoint periodically, 60 secs
[all …]
Djournalling.rst67 checkpoint all your transactions.
127 jbd2_journal_flush() // checkpoint everything.
Dxfs-self-describing-metadata.txt139 checkpoint and hence have some idea of how much modification occurred between
/Linux-v5.4/fs/jbd2/
DMakefile8 jbd2-objs := transaction.o commit.o recovery.o checkpoint.o revoke.o journal.o
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-fs-f2fs134 Controls the checkpoint timing.
174 ratio exceeds configured threshold, checkpoint will
251 If checkpoint=disable, it displays the number of blocks that are unusable.
252 If checkpoint=enable it displays the enumber of blocks that would be unusable
253 if checkpoint=disable were to be set.
Dsysfs-fs-nilfs2109 Show checkpoint number of the latest segment.
141 Show next checkpoint number.
230 Show checkpoint number of the latest segment.
236 Show next checkpoint number.
/Linux-v5.4/fs/f2fs/
DMakefile5 f2fs-y += checkpoint.o gc.o data.o node.o segment.o recovery.o
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Dera.rst35 checkpoint section in Messages
78 - Send a checkpoint message to the era target
/Linux-v5.4/drivers/net/ppp/
Dbsd_comp.c151 unsigned int checkpoint; /* when to next check the ratio */ member
230 db->checkpoint = CHECK_GAP; in bsd_clear()
251 if (db->in_count >= db->checkpoint) in bsd_check()
260 db->checkpoint = db->in_count + CHECK_GAP; in bsd_check()
/Linux-v5.4/Documentation/admin-guide/mm/
Dsoft-dirty.rst43 This feature is actively used by the checkpoint-restore project. You
/Linux-v5.4/fs/udf/
Decma_167.h572 __le32 checkpoint; member
798 __le32 checkpoint; member
Dinode.c1496 iinfo->i_checkpoint = le32_to_cpu(fe->checkpoint); in udf_read_inode()
1511 iinfo->i_checkpoint = le32_to_cpu(efe->checkpoint); in udf_read_inode()
1790 fe->checkpoint = cpu_to_le32(iinfo->i_checkpoint); in udf_update_inode()
1827 efe->checkpoint = cpu_to_le32(iinfo->i_checkpoint); in udf_update_inode()
/Linux-v5.4/drivers/mtd/ubi/
DKconfig69 only has to locate a checkpoint (called fastmap) on the device.
/Linux-v5.4/Documentation/admin-guide/cgroup-v1/
Dfreezer-subsystem.rst14 of tasks. The freezer allows the checkpoint code to obtain a consistent
/Linux-v5.4/kernel/power/
DKconfig45 system and powers it off; and restores that checkpoint on reboot.
/Linux-v5.4/init/
DKconfig1144 Enables additional kernel features in a sake of checkpoint/restore.