From: Dave Chinner <david@fromorbit.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Thumshirn <jth@kernel.org>,
Naohiro Aota <naohiro.aota@wdc.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v13 1/2] fs: New zonefs file system
Date: Fri, 7 Feb 2020 15:06:23 +1100 [thread overview]
Message-ID: <20200207040623.GE21953@dread.disaster.area> (raw)
In-Reply-To: <20200207031606.641231-2-damien.lemoal@wdc.com>
On Fri, Feb 07, 2020 at 12:16:05PM +0900, Damien Le Moal wrote:
> zonefs is a very simple file system exposing each zone of a zoned block
> device as a file. Unlike a regular file system with zoned block device
> support (e.g. f2fs), zonefs does not hide the sequential write
> constraint of zoned block devices to the user. Files representing
> sequential write zones of the device must be written sequentially
> starting from the end of the file (append only writes).
Looks good enough to merge from my perspective. There's little bits
that can be further tweaked and cleaned, but all the critical stuff
has been addressed and documented.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2020-02-07 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 3:16 [PATCH v13 0/2] New zonefs file system Damien Le Moal
2020-02-07 3:16 ` [PATCH v13 1/2] fs: " Damien Le Moal
2020-02-07 4:06 ` Dave Chinner [this message]
2020-02-07 3:16 ` [PATCH v13 2/2] zonefs: Add documentation Damien Le Moal
2020-02-20 0:55 ` Randy Dunlap
2020-02-20 0:59 ` Damien Le Moal
2020-02-20 1:15 ` Randy Dunlap
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=20200207040623.GE21953@dread.disaster.area \
--to=david@fromorbit.com \
--cc=damien.lemoal@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=hare@suse.de \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox