From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd
Date: Wed, 15 Nov 2023 22:39:39 +0000 [thread overview]
Message-ID: <bug-217965-13602-tWzo0214Oi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217965-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217965
--- Comment #26 from Eyal Lebedinsky (bugzilla@eyal.emu.id.au) ---
Ojaswin,
For my understanding: the (dirty) buffers hold data blocks that need to be
written. Clearing dirty buffers does not include fs activity,
which was already performed during the copy. Is this correct? If so then why
are we talking about ext4?
I expect that my understanding is incorrect.
The copy itself is very fast, completing in a few seconds.
I assume that the requested mount option is safe. Is it safe to use this way
$ sudo mount -o remount,nodelalloc /data1
or should I also add the other current options, 'noatime' (from fstab) and
'stripe=640' (automatic)?
or should I reboot with this option in fstab?
Below is what I did now, is this what you need?
$ sudo perf record -p 1366946 sleep 60
[ perf record: Woken up 37 times to write data ]
[ perf record: Captured and wrote 9.079 MB perf.data (237339 samples) ]
$ sudo perf report --no-children --stdio -i perf.data
# To display the perf.data header info, please use --header/--header-only
options.
#
#
# Total Lost Samples: 0
#
# Samples: 237K of event 'cycles:P'
# Event count (approx.): 258097341907
#
# Overhead Command Shared Object Symbol
# ........ ............... .................
..........................................
#
53.90% kworker/u16:4+f [kernel.kallsyms] [k] ext4_mb_good_group
13.71% kworker/u16:4+f [kernel.kallsyms] [k] ext4_get_group_info
7.39% kworker/u16:4+f [kernel.kallsyms] [k]
ext4_mb_find_good_group_avg_frag_lists
6.96% kworker/u16:4+f [kernel.kallsyms] [k] __rcu_read_unlock
5.01% kworker/u16:4+f [kernel.kallsyms] [k] ext4_mb_scan_aligned
4.51% kworker/u16:4+f [kernel.kallsyms] [k] __rcu_read_lock
1.70% kworker/u16:4+f [kernel.kallsyms] [k] mb_find_order_for_block
0.89% kworker/u16:4+f [kernel.kallsyms] [k] xas_descend
0.85% kworker/u16:4+f [kernel.kallsyms] [k] filemap_get_entry
0.81% kworker/u16:4+f [kernel.kallsyms] [k] ext4_mb_regular_allocator
0.77% kworker/u16:4+f [kernel.kallsyms] [k] ext4_mb_load_buddy_gfp
0.54% kworker/u16:4+f [kernel.kallsyms] [k] xas_load
0.50% kworker/u16:4+f [kernel.kallsyms] [k] ext4_mb_unload_buddy
0.42% kworker/u16:4+f [kernel.kallsyms] [k] _raw_read_unlock
0.40% kworker/u16:4+f [kernel.kallsyms] [k] mb_find_extent
0.40% kworker/u16:4+f [kernel.kallsyms] [k] _raw_spin_trylock
0.25% kworker/u16:4+f [kernel.kallsyms] [k] __filemap_get_folio
0.24% kworker/u16:4+f [kernel.kallsyms] [k] _raw_read_lock
0.13% kworker/u16:4+f [kernel.kallsyms] [k] xas_start
0.12% kworker/u16:4+f [kernel.kallsyms] [k] mb_find_buddy
0.10% kworker/u16:4+f [kernel.kallsyms] [k] pagecache_get_page
0.08% kworker/u16:4+f [kernel.kallsyms] [k] folio_mark_accessed
0.05% kworker/u16:4+f [kernel.kallsyms] [k] folio_test_hugetlb
0.04% kworker/u16:4+f [kernel.kallsyms] [k] _raw_spin_unlock
0.02% kworker/u16:4+f [kernel.kallsyms] [k] __cond_resched
0.02% kworker/u16:4+f [kernel.kallsyms] [k]
perf_adjust_freq_unthr_context
0.01% kworker/u16:4+f [kernel.kallsyms] [k] gen8_irq_handler
0.01% kworker/u16:4+f [kernel.kallsyms] [k] _raw_spin_lock
0.01% kworker/u16:4+f [kernel.kallsyms] [k] native_irq_return_iret
0.01% kworker/u16:4+f [kernel.kallsyms] [k] native_write_msr
0.01% kworker/u16:4+f [kernel.kallsyms] [k] timekeeping_advance
0.01% kworker/u16:4+f [kernel.kallsyms] [k] _raw_spin_lock_irqsave
0.01% kworker/u16:4+f [kernel.kallsyms] [k] native_read_msr
<then many zero% items>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-11-15 22:39 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 8:10 [Bug 217965] New: ext4(?) regression since 6.5.0 on sata hdd bugzilla-daemon
2023-10-02 8:52 ` [Bug 217965] " bugzilla-daemon
2023-10-02 8:56 ` bugzilla-daemon
2023-10-02 8:57 ` bugzilla-daemon
2023-10-02 15:22 ` bugzilla-daemon
2023-10-02 15:55 ` bugzilla-daemon
2023-10-03 6:50 ` bugzilla-daemon
2023-10-03 6:57 ` bugzilla-daemon
2023-10-03 11:04 ` bugzilla-daemon
2023-10-03 13:42 ` bugzilla-daemon
2023-10-03 14:23 ` bugzilla-daemon
2023-10-04 12:44 ` bugzilla-daemon
2023-10-04 17:23 ` bugzilla-daemon
2023-10-11 7:53 ` bugzilla-daemon
2023-10-11 16:07 ` bugzilla-daemon
2023-10-11 22:23 ` bugzilla-daemon
2023-10-17 10:45 ` bugzilla-daemon
2023-10-17 10:52 ` bugzilla-daemon
2023-10-20 10:24 ` bugzilla-daemon
2023-10-21 10:07 ` bugzilla-daemon
2023-11-13 22:46 ` bugzilla-daemon
2023-11-14 5:55 ` bugzilla-daemon
2023-11-14 6:47 ` bugzilla-daemon
2023-11-14 8:22 ` bugzilla-daemon
2023-11-14 10:29 ` bugzilla-daemon
2023-11-15 4:06 ` bugzilla-daemon
2023-11-15 17:27 ` bugzilla-daemon
2023-11-15 22:39 ` bugzilla-daemon [this message]
2023-11-16 3:15 ` bugzilla-daemon
2023-11-16 4:05 ` bugzilla-daemon
2023-11-16 4:31 ` bugzilla-daemon
2023-11-16 4:33 ` bugzilla-daemon
2023-11-16 19:33 ` bugzilla-daemon
2023-11-17 0:01 ` bugzilla-daemon
2023-11-17 0:44 ` bugzilla-daemon
2023-11-17 1:39 ` bugzilla-daemon
2023-11-17 1:40 ` bugzilla-daemon
2023-11-17 15:39 ` bugzilla-daemon
2023-11-17 23:52 ` bugzilla-daemon
2023-11-17 23:53 ` bugzilla-daemon
2023-11-17 23:57 ` bugzilla-daemon
2023-11-18 12:10 ` bugzilla-daemon
2023-11-18 13:17 ` bugzilla-daemon
2023-11-20 6:11 ` bugzilla-daemon
2023-11-20 8:48 ` bugzilla-daemon
2023-11-27 17:31 ` bugzilla-daemon
2023-12-03 7:33 ` bugzilla-daemon
2023-12-15 11:27 ` bugzilla-daemon
2023-12-23 0:56 ` bugzilla-daemon
2023-12-23 1:48 ` bugzilla-daemon
2023-12-23 12:46 ` bugzilla-daemon
2023-12-23 14:22 ` bugzilla-daemon
2023-12-23 15:47 ` bugzilla-daemon
2023-12-29 20:35 ` bugzilla-daemon
2023-12-29 20:51 ` bugzilla-daemon
2023-12-29 21:05 ` bugzilla-daemon
2023-12-29 22:11 ` bugzilla-daemon
2023-12-29 22:13 ` bugzilla-daemon
2023-12-29 23:07 ` bugzilla-daemon
2023-12-29 23:22 ` bugzilla-daemon
2024-01-02 4:44 ` bugzilla-daemon
2024-01-02 6:44 ` bugzilla-daemon
2024-01-04 5:38 ` bugzilla-daemon
2024-01-04 22:20 ` bugzilla-daemon
2024-01-06 2:11 ` bugzilla-daemon
2024-01-06 3:18 ` bugzilla-daemon
2024-01-07 2:56 ` bugzilla-daemon
2024-02-07 11:44 ` bugzilla-daemon
2024-03-12 20:27 ` bugzilla-daemon
2024-03-17 11:58 ` bugzilla-daemon
2024-03-18 4:45 ` bugzilla-daemon
2024-03-20 6:46 ` bugzilla-daemon
2024-03-23 8:53 ` bugzilla-daemon
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=bug-217965-13602-tWzo0214Oi@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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.