From: "François-Xavier Thomas" <fx.thomas@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Filipe Manana <fdmanana@kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Qu Wenruo <wqu@suse.com>
Subject: Re: Massive I/O usage from btrfs-cleaner after upgrading to 5.16
Date: Sat, 22 Jan 2022 19:20:55 +0100 [thread overview]
Message-ID: <CAEwRaO58oCzY4GjU3gCSru3Gq02GvGSdkg5hPwCKMwYcZ+cM2Q@mail.gmail.com> (raw)
In-Reply-To: <7802ff58-d08b-76d4-fcc7-c5d15d798b3b@gmx.com>
> https://pastebin.com/raw/p87HX6AF
The 7th patch doesn't seem to be having a noticeable improvement so far.
> So even with more fixes, we may just end up with more IO for autodefrag,
> purely because old code is not defragging as hard.
That's unfortunate, but thanks for having looked into it, at least
there's a known reason for the IO increase.
François-Xavier
next prev parent reply other threads:[~2022-01-22 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 10:06 Massive I/O usage from btrfs-cleaner after upgrading to 5.16 François-Xavier Thomas
2022-01-17 12:02 ` Filipe Manana
2022-01-17 16:59 ` Filipe Manana
2022-01-17 21:37 ` François-Xavier Thomas
2022-01-19 9:44 ` François-Xavier Thomas
2022-01-19 10:13 ` Filipe Manana
2022-01-20 11:37 ` François-Xavier Thomas
2022-01-20 11:44 ` Filipe Manana
2022-01-20 12:02 ` François-Xavier Thomas
2022-01-20 12:45 ` Qu Wenruo
2022-01-20 12:55 ` Filipe Manana
2022-01-20 17:46 ` Filipe Manana
2022-01-20 18:21 ` François-Xavier Thomas
2022-01-21 10:49 ` Filipe Manana
2022-01-21 19:39 ` François-Xavier Thomas
2022-01-21 23:34 ` Qu Wenruo
2022-01-22 18:20 ` François-Xavier Thomas [this message]
2022-01-24 7:00 ` Qu Wenruo
2022-01-25 20:00 ` François-Xavier Thomas
2022-01-25 23:29 ` Qu Wenruo
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=CAEwRaO58oCzY4GjU3gCSru3Gq02GvGSdkg5hPwCKMwYcZ+cM2Q@mail.gmail.com \
--to=fx.thomas@gmail.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.com \
/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).