linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naohiro Aota <naohiro.aota@wdc.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Naohiro Aota <naohiro.aota@wdc.com>
Subject: [PATCH v2 0/2] btrfs: test active zone tracking
Date: Thu, 29 Sep 2022 13:19:23 +0900	[thread overview]
Message-ID: <cover.1664419525.git.naohiro.aota@wdc.com> (raw)

This series adds a test for checking if an active zone tracking feature of
btrfs's zoned mode. The first patch introduces _zone_capacity() helper to
get the zone capacity of a specified zone. It rewrites btrfs/237 with the
helper and use the helper in a newly added test btrfs/292.

Changes:
- v2:
  - Rename to common/zoned.
  - Move _filter_blkzone_report() as well to common/zoned.
  - Drop _require_fio as it was already unnecessary.

Naohiro Aota (2):
  common: introduce zone_capacity() to return a zone capacity
  btrfs: test active zone tracking

 common/filter       |  13 -----
 common/zoned        |  39 +++++++++++++
 tests/btrfs/237     |   8 +--
 tests/btrfs/292     | 136 ++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/292.out |   2 +
 5 files changed, 179 insertions(+), 19 deletions(-)
 create mode 100644 common/zoned
 create mode 100755 tests/btrfs/292
 create mode 100644 tests/btrfs/292.out

-- 
2.37.3


             reply	other threads:[~2022-09-29  4:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  4:19 Naohiro Aota [this message]
2022-09-29  4:19 ` [PATCH v2 1/2] common: introduce zone_capacity() to return a zone capacity Naohiro Aota
2022-09-29  5:15   ` Zorro Lang
2022-09-30  6:19     ` Naohiro Aota
2022-09-29  4:19 ` [PATCH v2 2/2] btrfs: test active zone tracking Naohiro Aota
2022-09-29  6:01   ` Zorro Lang
2022-09-29 12:04     ` David Sterba
2022-09-29 14:06       ` Zorro Lang
2022-09-30  6:21         ` Naohiro Aota
2022-09-30  6:29     ` Naohiro Aota

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=cover.1664419525.git.naohiro.aota@wdc.com \
    --to=naohiro.aota@wdc.com \
    --cc=fstests@vger.kernel.org \
    --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 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).