From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Adam Borowski <kilobyte@angband.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: Do not use data_alloc_cluster in ssd mode
Date: Fri, 21 Jul 2017 17:16:25 +0200 [thread overview]
Message-ID: <2574118e-ac4d-9788-cf8f-f633d46cfd88@mendix.com> (raw)
In-Reply-To: <20170721144922.2zriwspqixh7yt3l@angband.pl>
On 07/21/2017 04:49 PM, Adam Borowski wrote:
> On Fri, Jul 21, 2017 at 01:47:11PM +0200, Hans van Kranenburg wrote:
>> The changes in here do the following:
>>
>> 1. Throw out the current ssd_spread behaviour.
>> 2. Move the current ssd behaviour to the ssd_spread option.
>> 3. Make ssd mode data allocation identical to tetris mode, like nossd.
>> 4. Adjust and clean up filesystem mount messages so that we can easily
>> identify if a kernel has this patch applied or not, when providing
>> support to end users.
>
>> Notes for whoever wants to backport this patch on their 4.9 LTS kernel:
>> * First apply commit 8a83665a "btrfs: drop the nossd flag when
>> remounting with -o ssd", or fixup the differences manually.
>
> It's 951e7966 in mainline. I see no 8a83665a anywhere -- most likely it's
> what you got after cherry-picking to 4.9.
Yes, that's exactly where it went wrong, thanks.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-07-21 15:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 11:47 [PATCH] Btrfs: Do not use data_alloc_cluster in ssd mode Hans van Kranenburg
2017-07-21 14:49 ` Adam Borowski
2017-07-21 15:16 ` Hans van Kranenburg [this message]
2017-07-21 15:50 ` Austin S. Hemmelgarn
2017-07-21 23:21 ` Hans van Kranenburg
2017-07-24 11:23 ` Austin S. Hemmelgarn
2017-07-24 14:25 ` David Sterba
2017-07-24 17:22 ` Hans van Kranenburg
2017-07-24 17:52 ` David Sterba
2017-07-24 17:56 ` Hans van Kranenburg
2017-07-24 18:01 ` Chris Mason
2017-07-24 18:41 ` David Sterba
2017-07-24 18:53 ` Chris Mason
2017-07-24 19:06 ` Austin S. Hemmelgarn
2017-07-24 19:18 ` Chris Mason
2017-07-24 22:42 ` Hans van Kranenburg
2017-07-26 13:27 ` David Sterba
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=2574118e-ac4d-9788-cf8f-f633d46cfd88@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=kilobyte@angband.pl \
--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).