linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: linux-fsdevel@vger.kernel.org
Cc: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v2 0/8] zonefs improvements
Date: Wed, 20 Apr 2022 11:35:37 +0900	[thread overview]
Message-ID: <20220420023545.3814998-1-damien.lemoal@opensource.wdc.com> (raw)

The first 2 patches of this series are bug fixes intended for 5.18. The
remaining patches improve zonefs zone resource accounting:
* Accounting of the number of sequential zone files that are write open
  is changed to be unconditional, regardless of the use of the
  explicit-open mount option.
* Add accounting for active sequential zone files, that is, maintian a
  count of the number of sequential zone files that are not empty nor
  full or that have an explicit open zone.
* Add sysfs attributes to export the above 2 counters as well as the
  device defined limits for open and active zone resources.

Changes from v1:
* Changed patch 6 to add lockdep_assert_held() in the function
  zonefs_account_active().
* Added Review tags.

Damien Le Moal (8):
  zonefs: Clear inode information flags on inode creation
  zonefs: Fix management of open zones
  zonefs: Rename super block information fields
  zonefs: Always do seq file write open accounting
  zonefs: Export open zone resource information through sysfs
  zonefs: Add active seq file accounting
  documentation: zonefs: Cleanup the mount options section
  documentation: zonefs: Document sysfs attributes

 Documentation/filesystems/zonefs.rst |  52 ++++++-
 fs/zonefs/Makefile                   |   2 +-
 fs/zonefs/super.c                    | 224 +++++++++++++++++++++------
 fs/zonefs/sysfs.c                    | 139 +++++++++++++++++
 fs/zonefs/zonefs.h                   |  18 ++-
 5 files changed, 381 insertions(+), 54 deletions(-)
 create mode 100644 fs/zonefs/sysfs.c

-- 
2.35.1


             reply	other threads:[~2022-04-20  2:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  2:35 Damien Le Moal [this message]
2022-04-20  2:35 ` [PATCH v2 1/8] zonefs: Clear inode information flags on inode creation Damien Le Moal
2022-04-20  3:58   ` Chaitanya Kulkarni
2022-04-20  8:40   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 2/8] zonefs: Fix management of open zones Damien Le Moal
2022-04-20  8:44   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 3/8] zonefs: Rename super block information fields Damien Le Moal
2022-04-20 10:48   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 4/8] zonefs: Always do seq file write open accounting Damien Le Moal
2022-04-20 10:49   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 5/8] zonefs: Export open zone resource information through sysfs Damien Le Moal
2022-04-20 10:52   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 6/8] zonefs: Add active seq file accounting Damien Le Moal
2022-04-20  7:50   ` Johannes Thumshirn
2022-04-20 10:54   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 7/8] documentation: zonefs: Cleanup the mount options section Damien Le Moal
2022-04-20 10:57   ` Hans Holmberg
2022-04-20  2:35 ` [PATCH v2 8/8] documentation: zonefs: Document sysfs attributes Damien Le Moal
2022-04-20 10:57   ` Hans Holmberg

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=20220420023545.3814998-1-damien.lemoal@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-fsdevel@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 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).