From: "Theodore Ts'o" <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: Alex Zhuravlev <bzzz@whamcloud.com>, "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH 0/4] ex4 block bitmap prefetching
Date: Fri, 17 Jul 2020 11:53:48 -0400 [thread overview]
Message-ID: <20200717155352.1053040-1-tytso@mit.edu> (raw)
I've revised Alex's original block allocation prefetch changes a bit,
and an option to prefetch all of the block allocation bitmaps when the
file system is mounted. Please take a look...
Alex Zhuravlev (2):
ext4: add prefetching for block allocation bitmaps
ext4: skip non-loaded groups at cr=0/1 when scanning for good groups
Theodore Ts'o (2):
ext4: indicate via a block bitmap read is prefetched via a tracepoint
ext4: add prefetch_block_bitmaps mount options
fs/ext4/balloc.c | 16 +++-
fs/ext4/ext4.h | 21 +++++-
fs/ext4/mballoc.c | 143 +++++++++++++++++++++++++++++++++++-
fs/ext4/super.c | 51 ++++++++++---
fs/ext4/sysfs.c | 4 +
include/trace/events/ext4.h | 24 +++++-
6 files changed, 236 insertions(+), 23 deletions(-)
--
2.24.1
next reply other threads:[~2020-07-17 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:53 Theodore Ts'o [this message]
2020-07-17 15:53 ` [PATCH 1/4] ext4: add prefetching for block allocation bitmaps Theodore Ts'o
2020-07-17 21:55 ` kernel test robot
2020-07-17 21:55 ` kernel test robot
2020-07-21 7:42 ` Andreas Dilger
2020-07-23 0:36 ` Shuichi Ihara
2020-07-23 15:00 ` tytso
2020-07-17 15:53 ` [PATCH 2/4] ext4: skip non-loaded groups at cr=0/1 when scanning for good groups Theodore Ts'o
2020-07-21 7:48 ` Andreas Dilger
2020-07-24 11:27 ` Благодаренко Артём
2020-07-17 15:53 ` [PATCH 3/4] ext4: indicate via a block bitmap read is prefetched via a tracepoint Theodore Ts'o
2020-07-21 7:51 ` Andreas Dilger
2020-07-24 12:04 ` Благодаренко Артём
2020-07-17 15:53 ` [PATCH 4/4] ext4: add prefetch_block_bitmaps mount options Theodore Ts'o
2020-07-21 8:20 ` Andreas Dilger
2020-07-24 13:58 ` Благодаренко Артём
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=20200717155352.1053040-1-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=bzzz@whamcloud.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.