From: hch <hch@lst.de>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: hch <hch@lst.de>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
David Sterba <dsterba@suse.com>, WenRuo Qu <wqu@suse.com>
Subject: Re: [PATCH RFC 0/1] btrfs: don't allocate data off of conventional zones
Date: Mon, 19 Jan 2026 07:48:57 +0100 [thread overview]
Message-ID: <20260119064857.GA1316@lst.de> (raw)
In-Reply-To: <fadec915-cb8c-4b0a-96f6-5b278d5789fc@wdc.com>
On Sat, Jan 17, 2026 at 09:46:49AM +0000, Johannes Thumshirn wrote:
> > The main intention behind this is, that we can handle metadata like
> > metadata on regular non zoned devices, including the ability to
> > overwrite it. But agreed I'd need to measure how much space we save this
> > way. The second motivation is that we can remove the faking of
> > sequential zones on conventional zones, aka the write pointer emulation
> > etc..
> One thing we could do here (and it shouldn't be easy as well) is,
> *prefer* sequential zones for data and conventional zones for metadata.
Absolutely.
next prev parent reply other threads:[~2026-01-19 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:57 [PATCH RFC 0/1] btrfs: don't allocate data off of conventional zones Johannes Thumshirn
2026-01-16 9:57 ` [PATCH RFC 1/1] btrfs: zoned: only allocate data off of sequential zones Johannes Thumshirn
2026-01-16 9:57 ` [PATCH RFC 1/2] btrfs-progs: collapse find_free_dev_extent into find_free_dev_extent_start Johannes Thumshirn
2026-01-16 9:57 ` [PATCH RFC 2/2] btrfs-progs: zoned: only allocate data off of sequential zones Johannes Thumshirn
2026-01-16 14:54 ` [PATCH RFC 0/1] btrfs: don't allocate data off of conventional zones Christoph Hellwig
2026-01-16 18:46 ` Johannes Thumshirn
2026-01-17 9:46 ` Johannes Thumshirn
2026-01-19 6:48 ` hch [this message]
2026-01-19 6:50 ` hch
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=20260119064857.GA1316@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=dlemoal@kernel.org \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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