From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Christoph Hellwig <hch@lst.de>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs zoned fixlets
Date: Fri, 25 Mar 2022 08:50:09 +0100 [thread overview]
Message-ID: <20220325075009.GA7096@lst.de> (raw)
In-Reply-To: <PH0PR04MB74167494E27155CC7667BF969B1A9@PH0PR04MB7416.namprd04.prod.outlook.com>
On Fri, Mar 25, 2022 at 07:35:57AM +0000, Johannes Thumshirn wrote:
> On 24/03/2022 17:55, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series fixes a minor and slightly less minor problem in the btrfs
> > zoned device code. Note that for the second patch the comment might
> > not be correct any more - AFAICS 5.18 added support for the dup
> > profile for zoned devices, which means we do have a real issue now
> > if different devices have different hardware limitations.
>
> It's not a problem, as a) DUP is not spanning multiple devices, but
> only used on one device and b) DUP is (as of now) only used on meta-data
> which can't use zone append.
Ok, in that case the comment that I wrote based on the 5.17-ish code
is still correct.
next prev parent reply other threads:[~2022-03-25 7:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 16:52 btrfs zoned fixlets Christoph Hellwig
2022-03-24 16:52 ` [PATCH 1/2] btrfs: remove the zoned/zone_size union in struct btrfs_fs_info Christoph Hellwig
2022-03-25 7:33 ` Johannes Thumshirn
2022-03-28 14:37 ` David Sterba
2022-03-28 12:46 ` Naohiro Aota
2022-03-28 19:01 ` David Sterba
2022-03-24 16:52 ` [PATCH 2/2] btrfs: fix and document the zoned device choice in alloc_new_bio Christoph Hellwig
2022-03-25 9:09 ` Johannes Thumshirn
2022-03-28 19:12 ` David Sterba
2022-03-28 23:04 ` Naohiro Aota
2022-03-30 15:10 ` David Sterba
2022-03-28 13:31 ` Naohiro Aota
2022-03-25 7:35 ` btrfs zoned fixlets Johannes Thumshirn
2022-03-25 7:50 ` Christoph Hellwig [this message]
2022-04-08 16:41 ` Christoph Hellwig
2022-04-08 16:50 ` David Sterba
2022-04-11 16:39 ` 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=20220325075009.GA7096@lst.de \
--to=hch@lst.de \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.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.