From: Stefan Wahren <stefan.wahren@i2se.com>
To: linux-ext4@vger.kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
Theodore Ts'o <tytso@mit.edu>,
Ritesh Harjani <riteshh@linux.ibm.com>,
linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geetika.Moolchandani1@ibm.com, regressions@lists.linux.dev
Subject: Re: [Regression] ext4: changes to mb_optimize_scan cause issues on Raspberry Pi
Date: Sun, 24 Jul 2022 23:43:38 +0200 [thread overview]
Message-ID: <a9c9a644-cdff-2ef8-11f9-da1d358847af@i2se.com> (raw)
In-Reply-To: <0d81a7c2-46b7-6010-62a4-3e6cfc1628d6@i2se.com>
Am 18.07.22 um 15:29 schrieb Stefan Wahren:
> Hi,
>
> i noticed that since Linux 5.18 (Linux 5.19-rc6 is still affected) i'm
> unable to run "rpi-update" without massive performance regression on
> my Raspberry Pi 4 (multi_v7_defconfig + CONFIG_ARM_LPAE). Using Linux
> 5.17 this tool successfully downloads the latest firmware (> 100 MB)
> on my development micro SD card (Kingston 16 GB Industrial) with a
> ext4 filesystem within ~ 1 min. The same scenario on Linux 5.18 shows
> the following symptoms:
>
FWIW, here some information about the affected ext4 partition:
fc stats:
0 commits
0 ineligible
0 numblks
0us avg_commit_time
Ineligible reasons:
"Extended attributes changed": 0
"Cross rename": 0
"Journal flag changed": 0
"Insufficient memory": 0
"Swap boot": 0
"Resize": 0
"Dir renamed": 0
"Falloc range op": 0
"Data journalling": 0
options:
rw
bsddf
nogrpid
block_validity
dioread_nolock
nodiscard
delalloc
nowarn_on_error
nojournal_checksum
barrier
auto_da_alloc
user_xattr
noquota
resuid=0
resgid=0
errors=continue
commit=5
min_batch_time=0
max_batch_time=15000
stripe=0
data=ordered
inode_readahead_blks=32
init_itable=10
max_dir_size_kb=0
tune2fs 1.44.5 (15-Dec-2018)
Filesystem volume name: rootfs
Last mounted on: /
Filesystem UUID: 3857a514-b0f4-49ce-8430-34762068bb6f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent flex_bg sparse_super large_file dir_nlink
extra_isize
Filesystem flags: unsigned_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 927360
Block count: 3755008
Reserved block count: 158603
Free blocks: 1770208
Free inodes: 731074
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 220
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8064
Inode blocks per group: 504
Flex block group size: 16
Filesystem created: Fri Mar 5 00:10:14 2021
Last mount time: Sun Jul 24 22:47:19 2022
Last write time: Sun Jul 24 22:47:18 2022
Mount count: 4
Maximum mount count: -1
Last checked: Tue Jul 19 09:16:29 2022
Check interval: 0 (<none>)
Lifetime writes: 25 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 4f95e9ae-24e1-4c7f-bb32-f4a9c41649a7
Journal backup: inode blocks
next prev parent reply other threads:[~2022-07-24 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 13:29 [Regression] ext4: changes to mb_optimize_scan cause issues on Raspberry Pi Stefan Wahren
2022-07-24 21:43 ` Stefan Wahren [this message]
2022-07-25 15:07 ` Ojaswin Mujoo
2022-07-25 19:09 ` Stefan Wahren
2022-07-26 6:43 ` Ojaswin Mujoo
2022-07-26 15:54 ` Stefan Wahren
2022-07-28 7:37 ` Thorsten Leemhuis
2022-07-28 10:00 ` Jan Kara
2022-07-29 5:30 ` Stefan Wahren
2022-07-31 20:42 ` Stefan Wahren
2022-08-06 15:23 ` Stefan Wahren
2022-08-14 10:07 ` Stefan Wahren
2022-08-15 10:34 ` Jan Kara
2022-08-15 11:03 ` Stefan Wahren
2022-08-06 9:50 ` Stefan Wahren
2022-08-16 9:34 ` Jan Kara
2022-08-16 11:25 ` Stefan Wahren
2022-08-16 20:45 ` Stefan Wahren
2022-08-17 5:24 ` Ojaswin Mujoo
2022-08-17 10:57 ` 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=a9c9a644-cdff-2ef8-11f9-da1d358847af@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=Geetika.Moolchandani1@ibm.com \
--cc=harshadshirwadkar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=regressions@lists.linux.dev \
--cc=riteshh@linux.ibm.com \
--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).