From: kusumi.tomohiro@gmail.com
To: axboe@kernel.dk, fio@vger.kernel.org
Cc: Tomohiro Kusumi <tkusumi@tuxera.com>
Subject: [PATCH] man page: add offset unit info for offset= option
Date: Tue, 27 Jun 2017 18:20:07 +0300 [thread overview]
Message-ID: <20170627152007.14839-1-tkusumi@tuxera.com> (raw)
From: Tomohiro Kusumi <tkusumi@tuxera.com>
Apply below commit to fio(1) man page.
82dbb8cb (HOWTO: add offset unit info for offset= option)
Certain sections/options of the man page are not in sync with HOWTO,
but this one was identical, thus the changes are the same as above.
--
On 06/27/2017 08:56 AM, Elliott, Robert (Persistent Memory) wrote:
>> HOWTO | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> The manpage (fio.1) should be updated as well - that's more visible to users.
Agree, I usually catch that.
Signed-off-by: Tomohiro Kusumi <tkusumi@tuxera.com>
---
fio.1 | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/fio.1 b/fio.1
index 6a6ea1b..ac87c9d 100644
--- a/fio.1
+++ b/fio.1
@@ -911,11 +911,13 @@ If true, use buffered I/O. This is the opposite of the \fBdirect\fR parameter.
Default: true.
.TP
.BI offset \fR=\fPint
-Start I/O at the provided offset in the file, given as either a fixed size or a
-percentage. If a percentage is given, the next \fBblockalign\fR-ed offset will
-be used. Data before the given offset will not be touched. This effectively
-caps the file size at (real_size - offset). Can be combined with \fBsize\fR to
-constrain the start and end range of the I/O workload.
+Start I/O at the provided offset in the file, given as either a fixed size in
+bytes or a percentage. If a percentage is given, the next \fBblockalign\fR-ed
+offset will be used. Data before the given offset will not be touched. This
+effectively caps the file size at (real_size - offset). Can be combined with
+\fBsize\fR to constrain the start and end range of the I/O workload. A percentage
+can be specified by the percentage number plus 1 with preceding '-'. For example,
+-1 is parsed as 0%, -10 is parsed as 9%, -101 is parsed as 100%.
.TP
.BI offset_increment \fR=\fPint
If this is provided, then the real offset becomes the
--
2.9.4
next reply other threads:[~2017-06-27 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 15:20 kusumi.tomohiro [this message]
2017-06-27 15:45 ` [PATCH] man page: add offset unit info for offset= option Jens Axboe
2017-06-27 15:41 kusumi.tomohiro
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=20170627152007.14839-1-tkusumi@tuxera.com \
--to=kusumi.tomohiro@gmail.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=tkusumi@tuxera.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 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.