public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Liu <chaoliu719@gmail.com>
To: Matthew Wilcox <willy@infradead.org>, Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yue Hu <huyue2@coolpad.com>, Wayne Zhang <zhangwen@coolpad.com>,
	Chao Liu <liuchao@coolpad.com>
Subject: Re: [PATCH v2] docs: filesystems: f2fs: fix description about compress ioctl
Date: Mon, 13 Jun 2022 16:02:00 +0800	[thread overview]
Message-ID: <Yqbu+BArbUNGvft9@liuchao-VM> (raw)
In-Reply-To: <Yqaw3VTD46PAMN8O@casper.infradead.org>

On Mon, Jun 13, 2022 at 04:37:01AM +0100, Matthew Wilcox wrote:
> On Mon, Jun 13, 2022 at 10:08:00AM +0800, Chao Liu wrote:
> > v2:
> > - s/file size/filesize/
>
> Why would you change it to be wrong?
>

This is a suggestion from Chao Yu. Maybe he has some other considerations.

Hi Chao,

Can you help with this question?

Thanks.

> >  Documentation/filesystems/f2fs.rst | 13 +++++++------
> >  1 file changed, 7 insertions(+), 6 deletions(-)
> >
> > diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
> > index ad8dc8c040a2..531b0f8a3946 100644
> > --- a/Documentation/filesystems/f2fs.rst
> > +++ b/Documentation/filesystems/f2fs.rst
> > @@ -818,10 +818,11 @@ Compression implementation
> >    Instead, the main goal is to reduce data writes to flash disk as much as
> >    possible, resulting in extending disk life time as well as relaxing IO
> >    congestion. Alternatively, we've added ioctl(F2FS_IOC_RELEASE_COMPRESS_BLOCKS)
> > -  interface to reclaim compressed space and show it to user after putting the
> > -  immutable bit. Immutable bit, after release, it doesn't allow writing/mmaping
> > -  on the file, until reserving compressed space via
> > -  ioctl(F2FS_IOC_RESERVE_COMPRESS_BLOCKS) or truncating filesize to zero.
> > +  interface to reclaim compressed space and show it to user after setting a
> > +  special flag to the inode. Once the compressed space is released, the flag
> > +  will block writing data to the file until either the compressed space is
> > +  reserved via ioctl(F2FS_IOC_RESERVE_COMPRESS_BLOCKS) or the filesize is
> > +  truncated to zero.
> >
> >  Compress metadata layout::
> >
> > @@ -830,12 +831,12 @@ Compress metadata layout::
> >  		| cluster 1 | cluster 2 | ......... | cluster N |
> >  		+-----------------------------------------------+
> >  		.           .                       .           .
> > -	.                       .                .                      .
> > +	  .                      .                .                      .
> >      .         Compressed Cluster       .        .        Normal Cluster            .
> >      +----------+---------+---------+---------+  +---------+---------+---------+---------+
> >      |compr flag| block 1 | block 2 | block 3 |  | block 1 | block 2 | block 3 | block 4 |
> >      +----------+---------+---------+---------+  +---------+---------+---------+---------+
> > -	    .                             .
> > +	       .                             .
> >  	    .                                           .
> >  	.                                                           .
> >  	+-------------+-------------+----------+----------------------------+
> > --
> > 2.36.1
> >

  reply	other threads:[~2022-06-13  8:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  2:08 [PATCH v2] docs: filesystems: f2fs: fix description about compress ioctl Chao Liu
2022-06-13  3:37 ` Matthew Wilcox
2022-06-13  8:02   ` Chao Liu [this message]
2022-06-13 17:23     ` Jonathan Corbet
2022-06-14  1:48       ` Chao Yu
2022-06-14  2:49       ` Chao Liu

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=Yqbu+BArbUNGvft9@liuchao-VM \
    --to=chaoliu719@gmail.com \
    --cc=chao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=huyue2@coolpad.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuchao@coolpad.com \
    --cc=willy@infradead.org \
    --cc=zhangwen@coolpad.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