From: Damien Le Moal <damien.lemoal@wdc.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] zonefs changes for 5.10-rc1
Date: Mon, 19 Oct 2020 08:25:41 +0900 [thread overview]
Message-ID: <20201018232541.87913-1-damien.lemoal@wdc.com> (raw)
Linus,
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs.git/ tags/zonefs-5.10-rc1
for you to fetch changes up to 48bfd5c6fac10e10b7066bf4aeb919ed9a4e87d3:
zonefs: document the explicit-open mount option (2020-09-15 18:32:58 +0900)
----------------------------------------------------------------
zonefs changes for 5.10
This pull request introduces the following changes to zonefs:
* Add the "explicit-open" mount option to automatically issue a
REQ_OP_ZONE_OPEN command to the device whenever a sequential zone file
is open for writing for the first time. This avoids "insufficient zone
resources" errors for write operations on some drives with limited
zone resources or on ZNS drives with a limited number of active zones.
From Johannes.
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
----------------------------------------------------------------
Johannes Thumshirn (4):
zonefs: introduce helper for zone management
zonefs: provide no-lock zonefs_io_error variant
zonefs: open/close zone on file open/close
zonefs: document the explicit-open mount option
Documentation/filesystems/zonefs.rst | 15 +++
fs/zonefs/super.c | 221 ++++++++++++++++++++++++++++++++---
fs/zonefs/zonefs.h | 10 ++
3 files changed, 233 insertions(+), 13 deletions(-)
next reply other threads:[~2020-10-18 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 23:25 Damien Le Moal [this message]
2020-10-19 21:46 ` [GIT PULL] zonefs changes for 5.10-rc1 pr-tracker-bot
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=20201018232541.87913-1-damien.lemoal@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.