From: Damien Le Moal <damien.lemoal@wdc.com>
To: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Thumshirn <jth@kernel.org>,
Naohiro Aota <naohiro.aota@wdc.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCH v4 0/2] New zonefs file system
Date: Wed, 25 Dec 2019 17:17:14 +0900 [thread overview]
Message-ID: <20191225081716.327348-1-damien.lemoal@wdc.com> (raw)
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 or the on-going btrfs effort), 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).
zonefs is not a POSIX compliant file system. It's goal is to simplify
the implementation of zoned block devices support in applications by
replacing raw block device file accesses with a richer file based API,
avoiding relying on direct block device file ioctls which may
be more obscure to developers. One example of this approach is the
implementation of LSM (log-structured merge) tree structures (such as
used in RocksDB and LevelDB) on zoned block devices by allowing SSTables
to be stored in a zone file similarly to a regular file system rather
than as a range of sectors of a zoned device. The introduction of the
higher level construct "one file is one zone" can help reducing the
amount of changes needed in the application while at the same time
allowing the use of zoned block devices with various programming
languages other than C.
zonefs IO management implementation uses the new iomap generic code.
Changes from v3:
* Fixed many typos in the documentation
* Use symbolic file permission macros instead of octal values
(checkpatch.pl complains about this)
Changes from v2:
* Address comments and suggestions from Darrick:
- Make the inode of OFFLINE and READONLY zones immutable when
mounting. Also do this during zone information check after an IO
error.
- Change super block CRC seed to ~0.
- Avoid potential compiler warning in zonefs_create_zgroup().
* Fixed endianness related compilation warning detected by kbuild bot.
Changes from v1:
* Fixed comment typo
* Improved documentation as suggested by Hannes
Damien Le Moal (2):
fs: New zonefs file system
zonefs: Add documentation
Documentation/filesystems/zonefs.txt | 215 +++++
MAINTAINERS | 10 +
fs/Kconfig | 1 +
fs/Makefile | 1 +
fs/zonefs/Kconfig | 9 +
fs/zonefs/Makefile | 4 +
fs/zonefs/super.c | 1166 ++++++++++++++++++++++++++
fs/zonefs/zonefs.h | 169 ++++
include/uapi/linux/magic.h | 1 +
9 files changed, 1576 insertions(+)
create mode 100644 Documentation/filesystems/zonefs.txt
create mode 100644 fs/zonefs/Kconfig
create mode 100644 fs/zonefs/Makefile
create mode 100644 fs/zonefs/super.c
create mode 100644 fs/zonefs/zonefs.h
--
2.24.1
Damien Le Moal (2):
fs: New zonefs file system
zonefs: Add documentation
Documentation/filesystems/zonefs.txt | 215 +++++
MAINTAINERS | 10 +
fs/Kconfig | 1 +
fs/Makefile | 1 +
fs/zonefs/Kconfig | 9 +
fs/zonefs/Makefile | 4 +
fs/zonefs/super.c | 1165 ++++++++++++++++++++++++++
fs/zonefs/zonefs.h | 169 ++++
include/uapi/linux/magic.h | 1 +
9 files changed, 1575 insertions(+)
create mode 100644 Documentation/filesystems/zonefs.txt
create mode 100644 fs/zonefs/Kconfig
create mode 100644 fs/zonefs/Makefile
create mode 100644 fs/zonefs/super.c
create mode 100644 fs/zonefs/zonefs.h
--
2.24.1
next reply other threads:[~2019-12-25 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 8:17 Damien Le Moal [this message]
2019-12-25 8:17 ` [PATCH v4 1/2] fs: New zonefs file system Damien Le Moal
2019-12-25 8:17 ` [PATCH v4 2/2] zonefs: Add documentation Damien Le Moal
2020-01-03 0:12 ` Darrick J. Wong
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=20191225081716.327348-1-damien.lemoal@wdc.com \
--to=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;
as well as URLs for NNTP newsgroup(s).