From: David Sterba <dsterba@suse.cz>
To: Naohiro Aota <Naohiro.Aota@wdc.com>
Cc: Anand Jain <anand.jain@oracle.com>, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>, Hannes Reinecke <hare@suse.com>,
Nikolay Borisov <nborisov@suse.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
Josef Bacik <josef@toxicpanda.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Matias Bjorling <Matias.Bjorling@wdc.com>
Subject: Re: [PATCH v3 03/27] btrfs: Check and enable HMZONED mode
Date: Tue, 20 Aug 2019 15:05:50 +0200 [thread overview]
Message-ID: <20190820130419.GP24086@suse.cz> (raw)
In-Reply-To: <20190820050737.ngyaamjkdmzvhlqj@naota.dhcp.fujisawa.hgst.com>
On Tue, Aug 20, 2019 at 02:07:37PM +0900, Naohiro Aota wrote:
> >>>>cannot be located over sequential zones and there is no guarantees that the
> >>>>device will have enough conventional zones to store this cache. Resolve
> >>>>this problem by disabling completely the space cache. This does not
> >>>>introduces any problems with sequential block groups: all the free space is
> >>>>located after the allocation pointer and no free space before the pointer.
> >>>>There is no need to have such cache.
> >>>>
> >>>>For the same reason, NODATACOW is also disabled.
> >>>>
> >>>>Also INODE_MAP_CACHE is also disabled to avoid preallocation in the
> >>>>INODE_MAP_CACHE inode.
> >>>
> >>> A list of incompatibility features with zoned devices. This need better
> >>> documentation, may be a table and its reason is better.
> >>
> >>Are you referring to the format of the commit message itself ? Or would you like
> >>to see a documentation added to Documentation/filesystems/btrfs.txt ?
> >
> > Documenting in the commit change log is fine. But it can be better
> > documented in a listed format as it looks like we have a list of
> > features which will be incompatible with zoned devices.
> >
> >more below..
>
> Sure. I will add a table in the next version.
>
> btrfs.txt seems not to have much there.
We don't use the in-kernel documentation, it's either the wiki or the
manual pages in btrfs-progs. The section 5 page contains some generic
topics, eg. the swapfile limitations are there.
next prev parent reply other threads:[~2019-08-20 13:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 9:30 [PATCH v3 00/27] btrfs zoned block device support Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 01/27] btrfs: introduce HMZONED feature flag Naohiro Aota
2019-08-16 4:49 ` Anand Jain
2019-08-08 9:30 ` [PATCH v3 02/27] btrfs: Get zone information of zoned block devices Naohiro Aota
2019-08-16 4:44 ` Anand Jain
2019-08-16 14:19 ` Damien Le Moal
2019-08-16 23:47 ` Anand Jain
2019-08-16 23:55 ` Damien Le Moal
2019-08-08 9:30 ` [PATCH v3 03/27] btrfs: Check and enable HMZONED mode Naohiro Aota
2019-08-16 5:46 ` Anand Jain
2019-08-16 14:23 ` Damien Le Moal
2019-08-16 23:56 ` Anand Jain
2019-08-17 0:05 ` Damien Le Moal
2019-08-20 5:07 ` Naohiro Aota
2019-08-20 13:05 ` David Sterba [this message]
2019-08-08 9:30 ` [PATCH v3 04/27] btrfs: disallow RAID5/6 in " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 05/27] btrfs: disallow space_cache " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 06/27] btrfs: disallow NODATACOW " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 07/27] btrfs: disable tree-log " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 08/27] btrfs: disable fallocate " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 09/27] btrfs: align device extent allocation to zone boundary Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 10/27] btrfs: do sequential extent allocation in HMZONED mode Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 11/27] btrfs: make unmirroed BGs readonly only if we have at least one writable BG Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 12/27] btrfs: ensure metadata space available on/after degraded mount in HMZONED Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 13/27] btrfs: reset zones of unused block groups Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 14/27] btrfs: limit super block locations in HMZONED mode Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 15/27] btrfs: redirty released extent buffers in sequential BGs Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 16/27] btrfs: serialize data allocation and submit IOs Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 17/27] btrfs: implement atomic compressed IO submission Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 18/27] btrfs: support direct write IO in HMZONED Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 19/27] btrfs: serialize meta IOs on HMZONED mode Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 20/27] btrfs: wait existing extents before truncating Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 21/27] btrfs: avoid async checksum/submit on HMZONED mode Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 22/27] btrfs: disallow mixed-bg in " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 23/27] btrfs: disallow inode_cache " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 24/27] btrfs: support dev-replace " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 25/27] btrfs: enable relocation " Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 26/27] btrfs: relocate block group to repair IO failure in HMZONED Naohiro Aota
2019-08-08 9:30 ` [PATCH v3 27/27] btrfs: enable to mount HMZONED incompat flag Naohiro Aota
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=20190820130419.GP24086@suse.cz \
--to=dsterba@suse.cz \
--cc=Damien.LeMoal@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hare@suse.com \
--cc=josef@toxicpanda.com \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nborisov@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).