From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: introduce FI_COMPRESS_RELEASED instead of using IMMUTABLE bit
Date: Mon, 7 Jun 2021 09:56:55 -0700 [thread overview]
Message-ID: <YL5P15nLsc/3GQOY@google.com> (raw)
In-Reply-To: <95b5669f-a521-5865-2089-320e2a2493de@kernel.org>
On 06/06, Chao Yu wrote:
> On 2021/5/26 4:49, Jaegeuk Kim wrote:
> > Once we release compressed blocks, we used to set IMMUTABLE bit. But it turned
> > out it disallows every fs operations which we don't need for compression.
> >
> > Let's just prevent writing data only.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> BTW, we need to expose .i_inline field to userspace since there is no
> way to check status of inode whether it has released blocks?
Need to add some in F2FS_IOC_GET_COMPRESS_OPTION?
>
> Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-06-07 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 20:49 [f2fs-dev] [PATCH 1/2] f2fs: let's allow compression for mmap files Jaegeuk Kim
2021-05-25 20:49 ` [f2fs-dev] [PATCH 2/2] f2fs: introduce FI_COMPRESS_RELEASED instead of using IMMUTABLE bit Jaegeuk Kim
2021-06-06 13:53 ` Chao Yu
2021-06-07 16:56 ` Jaegeuk Kim [this message]
2021-06-07 23:17 ` Chao Yu
2021-06-09 18:43 ` Jaegeuk Kim
2021-06-10 15:24 ` Chao Yu
2021-05-26 9:09 ` [f2fs-dev] [PATCH 1/2] f2fs: let's allow compression for mmap files Chao Yu
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=YL5P15nLsc/3GQOY@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).