diff options
author | Harshad Shirwadkar <harshadshirwadkar@gmail.com> | 2020-11-06 04:58:55 +0100 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2020-11-07 05:01:03 +0100 |
commit | a1e5e465b31d6015fccb359d99053b39e5180466 (patch) | |
tree | 2f996837b5e750345915bc37e0433508a1e21a78 /Documentation/filesystems | |
parent | jbd2: rename j_maxlen to j_total_len and add jbd2_journal_max_txn_bufs (diff) | |
download | linux-a1e5e465b31d6015fccb359d99053b39e5180466.tar.xz linux-a1e5e465b31d6015fccb359d99053b39e5180466.zip |
ext4: clean up the JBD2 API that initializes fast commits
This patch removes jbd2_fc_init() API and its related functions to
simplify enabling fast commits. With this change, the number of fast
commit blocks to use is solely determined by the JBD2 layer. So, we
move the default value for minimum number of fast commit blocks from
ext4/fast_commit.h to include/linux/jbd2.h. However, whether or not to
use fast commits is determined by the file system. The file system
just sets the fast commit feature using
jbd2_journal_set_features(). JBD2 layer then determines how many
blocks to use for fast commits (based on the value found in the JBD2
superblock).
Note that the JBD2 feature flag of fast commits is just an indication
that there are fast commit blocks present on disk. It doesn't tell
JBD2 layer about the intent of the file system of whether to it wants
to use fast commit or not. That's why, we blindly clear the fast
commit flag in journal_reset() after the recovery is done.
Suggested-by: Jan Kara <jack@suse.cz>
Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Link: https://lore.kernel.org/r/20201106035911.1942128-7-harshadshirwadkar@gmail.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'Documentation/filesystems')
0 files changed, 0 insertions, 0 deletions