From: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Subject: [PATCH v2 00/22] ext4 fast commit fixes
Date: Thu, 5 Nov 2020 19:58:49 -0800 [thread overview]
Message-ID: <20201106035911.1942128-1-harshadshirwadkar@gmail.com> (raw)
ext4: fast commit fixes
This patch series adds several code-only (no on disk format changes)
fixes for the fast commit code. I verified that there were no
regressions introduced by this patch series in xfstests auto and log
groups in fast_commit and 4k configurations.
Changes since V1:
- Broke couple of misc patches into separate patches
- Added a few new fixes:
- atomic update of mount flags
- no fast commits on aborted journal
- Dropped confusing fast commit mount options
- Dropped jbd2_fc_init()
Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Harshad Shirwadkar (22):
ext4: describe fast_commit feature flags
ext4: mark fc ineligible if inode gets evictied due to mem pressure
ext4: drop redundant calls ext4_fc_track_range
ext4: fixup ext4_fc_track_* functions' signature
jbd2: rename j_maxlen to j_total_len and add jbd2_journal_max_txn_bufs
ext4: clean up the JBD2 API that initializes fast commits
jbd2: drop jbd2_fc_init documentation
jbd2: don't use state lock during commit path
jbd2: don't pass tid to jbd2_fc_end_commit_fallback()
jbd2: add todo for a fast commit performance optimization
jbd2: don't touch buffer state until it is filled
jbd2: don't read journal->j_commit_sequence without taking a lock
ext4: dedpulicate the code to wait on inode that's being committed
ext4: fix code documentatioon
ext4: mark buf dirty before submitting fast commit buffer
ext4: remove unnecessary fast commit calls from ext4_file_mmap
ext4: fix inode dirty check in case of fast commits
ext4: disable fast commit with data journalling
ext4: issue fsdev cache flush before starting fast commit
ext4: make s_mount_flags modifications atomic
jbd2: don't start fast commit on aborted journal
ext4: cleanup fast commit mount options
Documentation/filesystems/ext4/journal.rst | 6 +
Documentation/filesystems/ext4/super.rst | 7 +
Documentation/filesystems/journalling.rst | 6 +-
fs/ext4/ext4.h | 66 +++++---
fs/ext4/extents.c | 7 +-
fs/ext4/fast_commit.c | 169 +++++++++++----------
fs/ext4/fast_commit.h | 6 +-
fs/ext4/file.c | 6 +-
fs/ext4/fsmap.c | 2 +-
fs/ext4/fsync.c | 2 +-
fs/ext4/inode.c | 19 +--
fs/ext4/mballoc.c | 4 +-
fs/ext4/namei.c | 61 ++++----
fs/ext4/super.c | 43 +++---
fs/jbd2/commit.c | 11 +-
fs/jbd2/journal.c | 138 +++++++++--------
fs/jbd2/recovery.c | 6 +-
fs/ocfs2/journal.c | 2 +-
include/linux/jbd2.h | 23 ++-
include/trace/events/ext4.h | 10 +-
20 files changed, 328 insertions(+), 266 deletions(-)
--
2.29.1.341.ge80a0c044ae-goog
next reply other threads:[~2020-11-06 3:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 3:58 Harshad Shirwadkar [this message]
2020-11-06 3:58 ` [PATCH v2 01/22] ext4: describe fast_commit feature flags Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 02/22] ext4: mark fc ineligible if inode gets evictied due to mem pressure Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 03/22] ext4: drop redundant calls ext4_fc_track_range Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 04/22] ext4: fixup ext4_fc_track_* functions' signature Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 05/22] jbd2: rename j_maxlen to j_total_len and add jbd2_journal_max_txn_bufs Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 06/22] ext4: clean up the JBD2 API that initializes fast commits Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 07/22] jbd2: drop jbd2_fc_init documentation Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 08/22] jbd2: don't use state lock during commit path Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 09/22] jbd2: don't pass tid to jbd2_fc_end_commit_fallback() Harshad Shirwadkar
2020-11-06 3:58 ` [PATCH v2 10/22] jbd2: add todo for a fast commit performance optimization Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 11/22] jbd2: don't touch buffer state until it is filled Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 12/22] jbd2: don't read journal->j_commit_sequence without taking a lock Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 13/22] ext4: dedpulicate the code to wait on inode that's being committed Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 14/22] ext4: fix code documentatioon Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 15/22] ext4: mark buf dirty before submitting fast commit buffer Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 16/22] ext4: remove unnecessary fast commit calls from ext4_file_mmap Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 17/22] ext4: fix inode dirty check in case of fast commits Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 18/22] ext4: disable fast commit with data journalling Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 19/22] ext4: issue fsdev cache flush before starting fast commit Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 20/22] ext4: make s_mount_flags modifications atomic Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 21/22] jbd2: don't start fast commit on aborted journal Harshad Shirwadkar
2020-11-06 3:59 ` [PATCH v2 22/22] ext4: cleanup fast commit mount options Harshad Shirwadkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201106035911.1942128-1-harshadshirwadkar@gmail.com \
--to=harshadshirwadkar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).