All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org,
	Damien Le Moal <damien.lemoal@wdc.com>
Subject: Re: [PATCH] btrfs-progs:  default to SINGLE profile on zoned devices
Date: Wed, 7 Jul 2021 16:50:48 +0200	[thread overview]
Message-ID: <20210707145048.GK2610@twin.jikos.cz> (raw)
In-Reply-To: <20210706091922.38650-1-johannes.thumshirn@wdc.com>

On Tue, Jul 06, 2021 at 06:19:22PM +0900, Johannes Thumshirn wrote:
> On zoned devices we're currently not supporting any other block group
> profile than the SINGLE profile, so pick it as default value otherwise a
> user would have to specify it manually at mkfs time for rotational zoned
> devices.

Yes this is annoying but careful with setting defaults, it's hard to
change them. And in case of zoned devices it will be possible to set
something else in the future so defaulting to single/single needs to be
justified in another way than "currently we don't support anything
else".

The SSD fallback to single is not showing as useful and there's ongoing
work to make it default to dup for metadata again. For consistency I'd
rather have simple logic for selecting defaults and give hints
eventually instead of checking random things in the system and then
selectin on behalf of the user. Unfortunatelly it's not that easy as
there are conflicting valid interests and we don't have defaults that
fits all scenarios.

  parent reply	other threads:[~2021-07-07 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  9:19 [PATCH] btrfs-progs: default to SINGLE profile on zoned devices Johannes Thumshirn
2021-07-06 13:41 ` Nikolay Borisov
2021-07-07 14:50 ` David Sterba [this message]
2021-07-07 15:01   ` Johannes Thumshirn
2021-07-12 19:16     ` Johannes Thumshirn
2021-07-30 14:09       ` 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=20210707145048.GK2610@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=damien.lemoal@wdc.com \
    --cc=dsterba@suse.com \
    --cc=johannes.thumshirn@wdc.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 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.