This patch series adds support for fast commits which is a simplified
version of the scheme proposed by Park and Shin, in their paper,
"iJournaling: Fine-Grained Journaling for Improving the Latency of
Fsync System Call"[1]. The basic idea of fast commits is to make JBD2
give the client file system an opportunity to perform a faster
commit. Only if the file system cannot perform such a commit
operation, then JBD2 should fall back to traditional commits.
Because JBD2 operates at block granularity, for every file system
metadata update it commits all the changed blocks are written to the
journal at commit time. This is inefficient because updates to some
blocks that JBD2 commits are derivable from some other blocks. For
example, if a new extent is added to an inode, then corresponding
updates to the inode table, the block bitmap, the group descriptor and
the superblock can be derived based on just the extent information and
the corresponding inode information. So, if we take this relationship
between blocks into account and replay the journalled blocks smartly,
we could increase performance of file system commits significantly.
Fast commits introduced in this patch have two main contributions:
(1) Making JBD2 fast commit aware, so that clients of JBD2 can
implement fast commits
(2) Add support in ext4 to use JBD2's new interfaces and implement
fast commits
Fast commit operation
---------------------
The new fast commit operation works by tracking file system deltas
since last commit in memory and committing these deltas to disk during
fsync(). Ext4 maintains directory entry updates in an in-memory
queue. Also, the inodes that have changed since last commit are
maintained in an in-memory queue. These queues are flushed to disk
during the commit time in a log-structured way. Fast commit area is
organized as a log of TAG-LENGTH-VALUE tuples with a special "tail"
tag marking the end of a commit. If certain operation prevents fast
commit from happening, the commit code falls back to JBD2 full commit
operation and thus invalidating all the fast commits since last full
commit. JBD2 provides new jbd2_fc_start() and jbd2_fc_stop() functions
to co-ordinate between JBD2's full commits and client file system's
fast commits.
Recovery operation
------------------
During recovery, JBD2 lets the client file system handle fast commit
blocks as it wants. After performing transaction replay, JBD2 invokes
client file system's recovery path handler. During the scan phase,
Ext4's recovery path handler determines the validity of fast commit
log by making sure CRC and TID of fast commits are valid. During the
replay phase, the recovery handler replays tags one by one. These
replay handlers are idempotent. Thus, if we crash in the middle of
recovery, Ext4 can restart the log replay and reach the identical
final state.
Testing
-------
e2fsprogs was updated to set fast commit feature flag and to ignore
fast commit blocks during e2fsck.
https://github.com/harshadjs/e2fsprogs.git
No regressions were introduced in smoke tests.
How to Use this feature?
-----------------------
This feature should not be used in production until corresponding
e2fsprogs changes are ready. These changes are being worked on at -
https://github.com/harshadjs/e2fsprogs.git. This feature can be set at
mkfs time. For testing purposes, this feature can also be enabled by
passing a mount time flag "fc_debug_force". This mount flag should
only be used for testing purposes and never for production.
Once enabled, fast commit information can be viewed in
/proc/fs/ext4/<dev>/fc_info.
Performance Evaluation
----------------------
Ext4 performance was compared with and without fast commits using
fsmark, dbench and filebench benchmarks with local file system and
over NFS. This is the summary of results:
|-----------+-------------------+----------------+----------------+--------|
| Benchmark | Config | No FC | FC | % diff |
|-----------+-------------------+----------------+----------------+--------|
| Fsmark | Local, 8 threads | 1475.1 files/s | 4309.8 files/s | +192.2 |
| Fsmark | NFS, 4 threads | 299.4 files/s | 409.45 files/s | +36.8 |
|-----------+-------------------+----------------+----------------+--------|
| Dbench | Local, 2 procs | 33.32 MB/s | 70.87 MB/s | +112.7 |
| Dbench | NFS, 2 procs | 8.84 MB/s | 11.88 MB/s | +34.4 |
|-----------+-------------------+----------------+----------------+--------|
| Dbench | Local, 10 procs | 90.48 MB/s | 110.12 MB/s | +21.7 |
| Dbench | NFS, 10 procs | 34.62 MB/s | 52.83 MB/s | +52.6 |
|-----------+-------------------+----------------+----------------+--------|
| FileBench | Local, 16 threads | 10442.3 ops/s | 18617.8 ops/s | +78.3 |
| | (Varmail) | | | |
| FileBench | NFS, 16 threads | 1531.3 ops/s | 2681.5 ops/s | +75.1 |
| | (Varmail) | | | |
|-----------+-------------------+----------------+----------------+--------|
NFS Performance Evaluation
--------------------------
NFS performs commit_metadata operation very frequently which resulted
in a linux kernel untar operation resulting in over ~180 journal
commits / second. The same untar operation results in 2.5 commits /
second. However, as the above table shows, the benefits that NFS sees
aren't as great as the local disk. The reason for that is the network
latency. Before fast commits, NFS was bottlenecked on journal commit
performance. However, with fast commits reducing that time
significantly, NFS performance now gets bottlenecked on network
latency. NFS running on networks with lower latency (< 300 us) will
see better performance than the NFS numbers reported above.
DAX Support
-----------
Fast commits helps improve Ext4 performance on DAX devices
too. However, there as an opportunity to do even better. Collaborating
with Rohan Kadekodi (rak@xxxxxxxxxxxxx) from UT Austin and Saurabh
Kadekodi (saukad@xxxxxxxxxx) from CMU, we have added synchronous fast
commits which write at byte granularity (instead of block
granularity). This is WIP available at -
https://github.com/harshadjs/linux/tree/fc-pmem-renewed. Doing this
way, we get stronger guarantees than current Ext4 very cheaply on
persistent memory devices.
Changes since V8
----------------
* Added procfs tracking for fast commits
* Improved recovery path
* Added mount option to turn fast commits on for testing purpose
* A few bugfixes
* Rebased on top of ext4 dev branch
[1] iJournaling: Fine-Grained Journaling for Improving the Latency of
Fsync System Call
https://www.usenix.org/conference/atc17/technical-sessions/presentation/park
Harshad Shirwadkar (9):
doc: update ext4 and journalling docs to include fast commit feature
ext4: add fast_commit feature and handling for extended mount options
ext4 / jbd2: add fast commit initialization
jbd2: add fast commit machinery
ext4: main fast-commit commit path
jbd2: fast commit recovery path
ext4: fast commit recovery path
ext4: add a mount opt to forcefully turn fast commits on
ext4: add fast commit stats in procfs
Documentation/filesystems/ext4/journal.rst | 66 +
Documentation/filesystems/journalling.rst | 28 +
fs/ext4/Makefile | 2 +-
fs/ext4/acl.c | 2 +
fs/ext4/balloc.c | 7 +-
fs/ext4/ext4.h | 95 +
fs/ext4/ext4_jbd2.c | 2 +-
fs/ext4/extents.c | 309 ++-
fs/ext4/extents_status.c | 24 +
fs/ext4/fast_commit.c | 2149 ++++++++++++++++++++
fs/ext4/fast_commit.h | 160 ++
fs/ext4/file.c | 10 +-
fs/ext4/fsync.c | 2 +-
fs/ext4/ialloc.c | 165 +-
fs/ext4/inode.c | 130 +-
fs/ext4/ioctl.c | 22 +-
fs/ext4/mballoc.c | 208 +-
fs/ext4/namei.c | 185 +-
fs/ext4/super.c | 81 +-
fs/ext4/sysfs.c | 2 +
fs/ext4/xattr.c | 3 +
fs/jbd2/commit.c | 61 +
fs/jbd2/journal.c | 238 ++-
fs/jbd2/recovery.c | 59 +-
include/linux/jbd2.h | 91 +-
include/trace/events/ext4.h | 228 ++-
26 files changed, 4164 insertions(+), 165 deletions(-)
create mode 100644 fs/ext4/fast_commit.c
create mode 100644 fs/ext4/fast_commit.h
--
2.28.0.681.g6f77f65b4e-goog
