From: Roman Mamedov <rm@romanrm.net>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: About free space fragmentation, metadata write amplification and (no)ssd
Date: Thu, 8 Jun 2017 23:47:37 +0500 [thread overview]
Message-ID: <20170608234737.2a1c8db0@natsu> (raw)
In-Reply-To: <3e8876c3-b8b9-0922-8962-17f6cf38b81d@knorrie.org>
On Thu, 8 Jun 2017 19:57:10 +0200
Hans van Kranenburg <hans.van.kranenburg@mendix.com> wrote:
> There is an improvement with subvolume delete + nossd that is visible
> between 4.7 and 4.9.
I don't remember if I asked before, but did you test on 4.4? The two latest
longterm series are 4.9 and 4.4. 4.7 should be abandoned and forgotten by now
really, certainly not used daily in production, it's not even listed on
kernel.org anymore. Also it's possible the 4.7 branch that you test did not
receive all the bugfix backports from mainline like the longterm series do.
> I have no idea what change between 4.7 and 4.9 is responsible for this, but
> it's good.
FWIW, this appears to be the big Btrfs change between 4.7 and 4.9 (in 4.8):
Btrfs: introduce ticketed enospc infrastructure
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=957780eb2788d8c218d539e19a85653f51a96dc1
--
With respect,
Roman
next prev parent reply other threads:[~2017-06-08 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 20:19 About free space fragmentation, metadata write amplification and (no)ssd Hans van Kranenburg
2017-04-08 21:55 ` Peter Grandi
2017-04-09 0:21 ` Hans van Kranenburg
2017-04-09 0:39 ` Hans van Kranenburg
2017-04-09 3:14 ` Kai Krakow
2017-04-09 20:48 ` Hans van Kranenburg
2017-04-09 6:38 ` Paul Jones
2017-04-09 8:43 ` Roman Mamedov
2017-04-09 18:10 ` Chris Murphy
2017-04-09 20:15 ` Hans van Kranenburg
2017-04-10 12:23 ` Austin S. Hemmelgarn
2017-04-10 22:59 ` Hans van Kranenburg
2017-04-11 11:33 ` Austin S. Hemmelgarn
2017-04-11 13:13 ` Kai Krakow
2017-05-28 0:59 ` Hans van Kranenburg
2017-05-28 3:54 ` Duncan
2017-06-08 17:57 ` Hans van Kranenburg
2017-06-08 18:47 ` Roman Mamedov [this message]
2017-06-08 19:19 ` Hans van Kranenburg
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=20170608234737.2a1c8db0@natsu \
--to=rm@romanrm.net \
--cc=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@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 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).