From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: util-linux@vger.kernel.org, Wang Shilong <wshilong@ddn.com>
Subject: Re: [PATCH] fstrim: document kernel return minlen explictly
Date: Fri, 19 Apr 2019 08:16:11 -0700 [thread overview]
Message-ID: <20190419151611.GA6755@magnolia> (raw)
In-Reply-To: <1555684640-23615-1-git-send-email-wshilong1991@gmail.com>
On Fri, Apr 19, 2019 at 11:37:20PM +0900, Wang Shilong wrote:
> From: Wang Shilong <wshilong@ddn.com>
>
> Filesystem will modify @minlen according to its
> block size etc, and will return actual unit
> to userspace, document it into manpage.
>
> Cc: Darrick J. Wong <darrick.wong@oracle.com>
> Signed-off-by: Wang Shilong <wshilong@ddn.com>
> ---
> sys-utils/fstrim.8 | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/sys-utils/fstrim.8 b/sys-utils/fstrim.8
> index f7e7aa9ef..10ef8bc23 100644
> --- a/sys-utils/fstrim.8
> +++ b/sys-utils/fstrim.8
> @@ -76,10 +76,10 @@ the end of the filesystem.
> .IP "\fB\-m, \-\-minimum\fP \fIminimum-size\fP"
> Minimum contiguous free range to discard, in bytes. (This value is internally
> rounded up to a multiple of the filesystem block size.) Free ranges smaller
> -than this will be ignored. By increasing this value, the fstrim operation
> -will complete more quickly for filesystems with badly fragmented freespace,
> -although not all blocks will be discarded. The default value is zero,
> -discarding every free block.
> +than this will be ignored and kernel shall return modified value(fstrim_range.minlen)
Overly long line, and perhaps there should be a space between "value"
and "(fstrim_range.minlen)"?
> +to userspace.
What is the modified value? You might as well say that fitrim will
adjust the minimum if it's smaller than the device's minimum, and report
that back to userspace.
> By increasing this value, the fstrim operation will complete
> +more quickly for filesystems with badly fragmented freespace, although not
> +all blocks will be discarded. The default value is zero, discarding every free block.
I prefer the practice of starting each sentence in the manpage source on
a new line so that the diff only reflects changes to actual content (and
not just reflowing of the text)... but the sys-utils maintainers clearly
don't employ that convention so I guess this is ok. :)
Thanks for putting together the documentation update.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> .IP "\fB\-v, \-\-verbose\fP"
> Verbose execution. With this option
> .B fstrim
> --
> 2.21.0
>
prev parent reply other threads:[~2019-04-19 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 14:37 [PATCH] fstrim: document kernel return minlen explictly Wang Shilong
2019-04-19 15:16 ` Darrick J. Wong [this message]
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=20190419151611.GA6755@magnolia \
--to=darrick.wong@oracle.com \
--cc=util-linux@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
--cc=wshilong@ddn.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;
as well as URLs for NNTP newsgroup(s).