Received-SPF: pass (google.com: domain of linux-ext4+bounces-735-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd
Date: Sun, 07 Jan 2024 02:56:44 +0000
Message-ID: <bug-217965-13602-qyI8Zuxh5M@https.bugzilla.kernel.org/>
In-Reply-To: <bug-217965-13602@https.bugzilla.kernel.org/>
References: <bug-217965-13602@https.bugzilla.kernel.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0

https://bugzilla.kernel.org/show_bug.cgi?id=3D217965

--- Comment #65 from Matthew Stapleton (matthew4196@gmail.com) ---
I'm not sure if this will be worth looking into, but with the cpu usage
problem, I've done some more testing and "perf report --stdio -i perf.data"=
 is
showing around 2 to 3 times as much cpu time since the commit that added the
CR_BEST_AVAIL_LEN feature: 7e170922f06bf .  With
/sys/fs/ext4/<dev>/mb_best_avail_max_trim_order set to 0 it goes a bit lowe=
r,
but is still at least 2 times cpu.  With perf record -ag sleep 25 which is =
the
time it takes the extract to run, it's goes from about 2% to 5% so fairly
small, but when measuring with 5 second intervals this can go from around 5=
% to
15%.  This cpu usage is concentrated in ext4_get_group_desc and
ext4_get_group_info and within these functions, perf is picking up more cpu
time in __rcu_read_lock and __rcu_read_unlock.

--=20
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.=