From: Ankit Kumar <ankit.kumar@samsung.com>
To: axboe@kernel.dk
Cc: fio@vger.kernel.org, krish.reddy@samsung.com,
prakash.v@samsung.com, Ankit Kumar <ankit.kumar@samsung.com>
Subject: [PATCH 1/2] HOWTO: Add missing documentation for job_max_open_zones
Date: Wed, 4 Aug 2021 14:54:49 +0530 [thread overview]
Message-ID: <20210804092450.28782-2-ankit.kumar@samsung.com> (raw)
In-Reply-To: <20210804092450.28782-1-ankit.kumar@samsung.com>
---
HOWTO | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/HOWTO b/HOWTO
index 59c7f1ff..d4e620de 100644
--- a/HOWTO
+++ b/HOWTO
@@ -1055,6 +1055,11 @@ Target file/device
number of open zones is defined as the number of zones to which write
commands are issued.
+.. option:: job_max_open_zones=int
+
+ Limit on the number of simultaneously opened zones per single
+ thread/process.
+
.. option:: zone_reset_threshold=float
A number between zero and one that indicates the ratio of logical
--
2.30.0-rc0
next prev parent reply other threads:[~2021-08-04 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210804092848epcas5p43713e1728116d2ea38c910a2b8991c42@epcas5p4.samsung.com>
2021-08-04 9:24 ` [PATCH 0/2] v2: ZBD fix with random zone index logic and missing documentation Ankit Kumar
2021-08-04 9:24 ` Ankit Kumar [this message]
2021-08-04 9:24 ` [PATCH 2/2] zbd: Improve random zone index generation logic Ankit Kumar
2021-08-04 11:07 ` [PATCH 0/2] v2: ZBD fix with random zone index logic and missing documentation Shinichiro Kawasaki
2021-08-04 13:25 ` Jens Axboe
[not found] <CGME20210804112707epcas5p1b0bc0d3e4e85bcff47d4021359151a32@epcas5p1.samsung.com>
2021-08-04 11:23 ` [PATCH 0/2] v3: " Ankit Kumar
2021-08-04 11:23 ` [PATCH 1/2] HOWTO: Add missing documentation for job_max_open_zones Ankit Kumar
2021-08-04 12:01 ` Shinichiro Kawasaki
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=20210804092450.28782-2-ankit.kumar@samsung.com \
--to=ankit.kumar@samsung.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=krish.reddy@samsung.com \
--cc=prakash.v@samsung.com \
/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