All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Eric Levy <contact@ericlevy.name>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: "hardware-assisted zeroing"
Date: Tue, 4 Jan 2022 21:20:16 -0500	[thread overview]
Message-ID: <YdUAYId7qCY1MCAb@hungrycats.org> (raw)
In-Reply-To: <9dbeb4327f5e42f0fd45ee4a348bff3f34c6e3f9.camel@ericlevy.name>

On Tue, Jan 04, 2022 at 08:37:54PM -0500, Eric Levy wrote:
> On Tue, 2022-01-04 at 20:33 -0500, Zygo Blaxell wrote:
> 
> > That's up to the host filesystem implementation.  ZNS devices require
> > filesystems that speak ZNS protocol.  They don't implement a
> > traditional
> > LBA-oriented interface (or if they do, they provide a separate
> > logical
> > device interface for that).
> 
> The entire file system must fit on one device, even the allocation
> data. How would the host find the allocation information, if its
> location has been remapped?

For ZBD devices, a linear read of a superblock log zone can provide the
root pointer for the filesystem.  The rest of the trees arise from that
root.  ZNS filesystems can do something similar.

The location of the data is not entirely unknown.  It is written somewhere
within the zone designated by the filesystem--only the bottom N bits
are filled in by the device.

  reply	other threads:[~2022-01-05  2:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 11:08 "hardware-assisted zeroing" Eric Levy
2022-01-03 11:17 ` Qu Wenruo
2022-01-03 11:24   ` Eric Levy
2022-01-03 11:51     ` Qu Wenruo
2022-01-04 10:50       ` Eric Levy
2022-01-04 20:49         ` Zygo Blaxell
2022-01-04 22:37           ` Eric Levy
2022-01-04 22:46             ` Qu Wenruo
2022-01-05  0:38               ` Paul Jones
2022-01-05  0:44                 ` Eric Levy
2022-01-05  1:12                   ` Paul Jones
2022-01-05  1:20                     ` Eric Levy
2022-01-05  1:21                   ` Zygo Blaxell
2022-01-05  1:26                     ` Eric Levy
2022-01-05  1:33                       ` Zygo Blaxell
2022-01-05  1:37                         ` Eric Levy
2022-01-05  2:20                           ` Zygo Blaxell [this message]
2022-01-05  1:32             ` Zygo Blaxell
2022-01-04 22:37         ` Qu Wenruo
2022-01-03 11:46 ` David Disseldorp
2022-01-03 11:57   ` Qu Wenruo

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=YdUAYId7qCY1MCAb@hungrycats.org \
    --to=ce3g8jdj@umail.furryterror.org \
    --cc=contact@ericlevy.name \
    --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.