All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: Do not use data_alloc_cluster in ssd mode
Date: Mon, 24 Jul 2017 19:22:03 +0200	[thread overview]
Message-ID: <92250c4b-f2ee-a7d5-b247-0e8d3bb7f81f@mendix.com> (raw)
In-Reply-To: <20170724142508.GW2866@twin.jikos.cz>

On 07/24/2017 04:25 PM, David Sterba wrote:
> On Fri, Jul 21, 2017 at 01:47:11PM +0200, Hans van Kranenburg wrote:
>> [...]
>>
>>     So what now...?
>>
>> 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.
>>
>> Instead of directly cutting out all code related to the data cluster, it
>> makes sense to take a gradual approach and allow users who are still
>> able to find a valid reason to prefer the current ssd mode the means to
>> do so by specifiying the additional ssd_spread option.
>>
>> Since there are other uses of the ssd mode, we keep the difference
>> between nossd and ssd mode. However, the usage of the rotational
>> attribute warrants some reconsideration in the future.
>>
>> [...]
>> Signed-off-by: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
> 
> Thanks for the extensive historical summary, this change really deserves
> it.
> 
> Decoupling the assumptions about the device's block management is really
> a good thing, mount option 'ssd' should mean that the device just has
> cheap seeks. Moving the the allocation tweaks to ssd_spread provides a
> way to keep the behaviour for anybody who wants it.
> 
> I'd like to push this change to 4.13-rc3, as I don't think we need more
> time to let other users to test this. The effects of current ssd
> implementation have been debated and debugged on IRC for a long time.
> 
> Reviewed-by: David Sterba <dsterba@suse.com>
> 

Ok, thanks. I'll send out a v2 tonight with the typo / commit id fixes
etc from the other feedback.

-- 
Hans van Kranenburg

  reply	other threads:[~2017-07-24 17:22 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
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 [this message]
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=92250c4b-f2ee-a7d5-b247-0e8d3bb7f81f@mendix.com \
    --to=hans.van.kranenburg@mendix.com \
    --cc=dsterba@suse.cz \
    --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 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.