From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"dsterba@suse.com" <dsterba@suse.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Fixes for zoned mode
Date: Thu, 4 Mar 2021 13:54:59 +0000 [thread overview]
Message-ID: <PH0PR04MB7416588309F7A1A4A9E55AB49B979@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: cover.1614760899.git.naohiro.aota@wdc.com
On 04/03/2021 02:50, Naohiro Aota wrote:
> These are fixes for zoned btrfs.
>
> Patch 01 fixes the type of a zone sector variable.
>
> Patch 02 moves the superblock location to address based.
>
> Patch 03 fixes zone_unusable acconting when a block group is read-only.
>
> v1 -> v2:
> - Move the type fix patch to be the first one
> - Fix the type of variable instead of casting
> - Introduce #define's for the superblock zone locations and maximum zone
> size
>
> Naohiro Aota (3):
> btrfs: zoned: use sector_t to get zone sectors
> btrfs: zoned: move superblock logging zone location
> btrfs: zoned: do not account freed region of read-only block group as
> zone_unusable
>
> fs/btrfs/free-space-cache.c | 7 ++++++-
> fs/btrfs/zoned.c | 39 +++++++++++++++++++++++++++++--------
> 2 files changed, 37 insertions(+), 9 deletions(-)
>
For the whole series:
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
prev parent reply other threads:[~2021-03-04 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 8:55 [PATCH v2 0/3] Fixes for zoned mode Naohiro Aota
2021-03-03 8:55 ` [PATCH v2 1/3] btrfs: zoned: use sector_t to get zone sectors Naohiro Aota
2021-03-04 14:30 ` David Sterba
2021-03-03 8:55 ` [PATCH v2 2/3] btrfs: zoned: move superblock logging zone location Naohiro Aota
2021-03-04 15:14 ` David Sterba
2021-03-04 23:00 ` Damien Le Moal
2021-03-03 8:55 ` [PATCH v2 3/3] btrfs: zoned: do not account freed region of read-only block group as zone_unusable Naohiro Aota
2021-03-04 13:54 ` Johannes Thumshirn [this message]
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=PH0PR04MB7416588309F7A1A4A9E55AB49B979@PH0PR04MB7416.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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.