linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Chao Liu <chaoliu719@gmail.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Chao Liu <liuchao@coolpad.com>,
	linux-kernel@vger.kernel.org, Wayne Zhang <zhangwen@coolpad.com>,
	Yue Hu <huyue2@coolpad.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] docs: filesystems: f2fs: fix description about compress ioctl
Date: Fri, 10 Jun 2022 21:05:57 +0800	[thread overview]
Message-ID: <0e451780-31c8-b1e9-0205-b9e68a57e958@kernel.org> (raw)
In-Reply-To: <20220602072540.998638-1-chaoliu719@gmail.com>

On 2022/6/2 15:25, Chao Liu wrote:
> From: Chao Liu <liuchao@coolpad.com>
> 
> Since commit c61404153eb6 ("f2fs: introduce FI_COMPRESS_RELEASED
> instead of using IMMUTABLE bit"), we no longer use the IMMUTABLE
> bit to prevent writing data for compression. Let's correct the
> corresponding documentation.
> 
> BTW, this patch fixes some alignment issues in the compress
> metadata layout.
> 
> Signed-off-by: Chao Liu <liuchao@coolpad.com>
> ---
>   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..98dc24f5c6f0 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 file size is

s/file size/filesize/

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

> +  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 |
>       +----------+---------+---------+---------+  +---------+---------+---------+---------+
> -	    .                             .
> +	       .                             .
>   	    .                                           .
>   	.                                                           .
>   	+-------------+-------------+----------+----------------------------+


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  7:25 [f2fs-dev] [PATCH] docs: filesystems: f2fs: fix description about compress ioctl Chao Liu
2022-06-10 13:05 ` Chao Yu [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=0e451780-31c8-b1e9-0205-b9e68a57e958@kernel.org \
    --to=chao@kernel.org \
    --cc=chaoliu719@gmail.com \
    --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=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;
as well as URLs for NNTP newsgroup(s).