From: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, jack@suse.cz,
Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Subject: [PATCH 00/10] Ext4 fast commit fixes
Date: Sat, 31 Oct 2020 13:05:08 -0700 [thread overview]
Message-ID: <20201031200518.4178786-1-harshadshirwadkar@gmail.com> (raw)
ext4: fast commit fixes
This patch series adds several documentation and 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. Thanks Jan for
suggesting most of the fixes.
Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Harshad Shirwadkar (10):
ext4: describe fast_commit feature flags
ext4: mark fc ineligible if inode gets evictied due to mem pressure
ext4: pass handle to ext4_fc_track_* functions
ext4: clean up the JBD2 API that initializes fast commits
jbd2: fix fast commit journalling APIs
ext4: dedpulicate the code to wait on inode that's being committed
ext4: misc fast commit fixes
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
Documentation/filesystems/ext4/journal.rst | 6 +
Documentation/filesystems/ext4/super.rst | 7 ++
fs/ext4/ext4.h | 22 ++--
fs/ext4/ext4_jbd2.h | 6 +-
fs/ext4/extents.c | 11 +-
fs/ext4/fast_commit.c | 138 ++++++++++-----------
fs/ext4/fast_commit.h | 3 +-
fs/ext4/file.c | 2 -
fs/ext4/inode.c | 14 +--
fs/ext4/namei.c | 50 ++++----
fs/ext4/super.c | 5 +-
fs/jbd2/commit.c | 11 +-
fs/jbd2/journal.c | 94 ++++++++------
fs/jbd2/recovery.c | 2 +-
include/linux/jbd2.h | 13 +-
include/trace/events/ext4.h | 10 +-
16 files changed, 220 insertions(+), 174 deletions(-)
--
2.29.1.341.ge80a0c044ae-goog
next reply other threads:[~2020-10-31 20:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 20:05 Harshad Shirwadkar [this message]
2020-10-31 20:05 ` [PATCH 01/10] ext4: describe fast_commit feature flags Harshad Shirwadkar
2020-11-03 10:33 ` Jan Kara
2020-10-31 20:05 ` [PATCH 02/10] ext4: mark fc ineligible if inode gets evictied due to mem pressure Harshad Shirwadkar
2020-11-03 14:13 ` Jan Kara
2020-11-03 18:33 ` harshad shirwadkar
2020-11-04 9:52 ` Jan Kara
2020-10-31 20:05 ` [PATCH 03/10] ext4: pass handle to ext4_fc_track_* functions Harshad Shirwadkar
2020-11-03 14:46 ` Jan Kara
2020-11-05 1:53 ` harshad shirwadkar
2020-10-31 20:05 ` [PATCH 04/10] ext4: clean up the JBD2 API that initializes fast commits Harshad Shirwadkar
2020-11-03 16:29 ` Jan Kara
2020-11-04 19:52 ` harshad shirwadkar
2020-11-05 10:30 ` Jan Kara
2020-11-05 12:44 ` Jan Kara
[not found] ` <CAE1WUT6oxiKtrdF6vzLv5vYFxPjefRhzDE2xfQGF6CqQQdPv1Q@mail.gmail.com>
2020-11-06 3:02 ` harshad shirwadkar
2020-10-31 20:05 ` [PATCH 05/10] jbd2: fix fast commit journalling APIs Harshad Shirwadkar
2020-11-03 16:38 ` Jan Kara
2020-11-04 21:25 ` harshad shirwadkar
2020-10-31 20:05 ` [PATCH 06/10] ext4: dedpulicate the code to wait on inode that's being committed Harshad Shirwadkar
2020-11-03 16:42 ` Jan Kara
2020-11-04 21:35 ` harshad shirwadkar
2020-10-31 20:05 ` [PATCH 07/10] ext4: misc fast commit fixes Harshad Shirwadkar
2020-11-03 16:52 ` Jan Kara
2020-11-06 3:07 ` harshad shirwadkar
2020-10-31 20:05 ` [PATCH 08/10] ext4: fix inode dirty check in case of fast commits Harshad Shirwadkar
2020-11-01 7:09 ` Andrea Righi
2020-11-03 16:58 ` Jan Kara
2020-10-31 20:05 ` [PATCH 09/10] ext4: disable fast commit with data journalling Harshad Shirwadkar
2020-11-03 17:01 ` Jan Kara
2020-10-31 20:05 ` [PATCH 10/10] ext4: issue fsdev cache flush before starting fast commit Harshad Shirwadkar
2020-11-03 17:02 ` Jan Kara
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=20201031200518.4178786-1-harshadshirwadkar@gmail.com \
--to=harshadshirwadkar@gmail.com \
--cc=jack@suse.cz \
--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).