From: Chao Yu <chao@kernel.org>
To: Fengnan Chang <changfengnan@vivo.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 2/2] f2fs: support POSIX_FADV_DONTNEED drop compressed page cache
Date: Fri, 26 Nov 2021 23:21:03 +0800 [thread overview]
Message-ID: <bc37d799-ae77-9ab7-14a3-a70fccb0d454@kernel.org> (raw)
In-Reply-To: <20211126101921.305013-2-changfengnan@vivo.com>
On 2021/11/26 18:19, Fengnan Chang wrote:
> Previously, compressed page cache drop when clean page cache, but
> POSIX_FADV_DONTNEED can't clean compressed page cache because raw page
> don't have private data, and won't call f2fs_invalidate_compress_pages.
> This commit call f2fs_invalidate_compress_pages() directly in
> f2fs_file_fadvise() for POSIX_FADV_DONTNEED case.
>
> Signed-off-by: Fengnan Chang <changfengnan@vivo.com>
> ---
> fs/f2fs/file.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 32c0bd545c5c..dafdaad9a9e4 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -4677,12 +4677,11 @@ static ssize_t f2fs_file_write_iter(struct kiocb *iocb, struct iov_iter *from)
> static int f2fs_file_fadvise(struct file *filp, loff_t offset, loff_t len,
> int advice)
> {
> - struct inode *inode;
> struct address_space *mapping;
> struct backing_dev_info *bdi;
> + struct inode *inode = file_inode(filp);
>
> if (advice == POSIX_FADV_SEQUENTIAL) {
> - inode = file_inode(filp);
> if (S_ISFIFO(inode->i_mode))
> return -ESPIPE;
>
> @@ -4697,6 +4696,10 @@ static int f2fs_file_fadvise(struct file *filp, loff_t offset, loff_t len,
> filp->f_mode &= ~FMODE_RANDOM;
> spin_unlock(&filp->f_lock);
> return 0;
> + } else if (advice == POSIX_FADV_DONTNEED) {
> + if (test_opt(F2FS_I_SB(inode), COMPRESS_CACHE) &&
> + f2fs_compressed_file(inode))
> + f2fs_invalidate_compress_pages(F2FS_I_SB(inode), inode->i_ino);
> }
Well, how about invalidating compressed pages after generic_fadvise() in order to
check inode status before dropping caches?
Thanks,
>
> return generic_fadvise(filp, offset, len, advice);
>
_______________________________________________
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-11-26 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 10:19 [f2fs-dev] [PATCH v2 1/2] f2fs: fix remove page failed in invalidate compress pages Fengnan Chang
2021-11-26 10:19 ` [f2fs-dev] [PATCH v2 2/2] f2fs: support POSIX_FADV_DONTNEED drop compressed page cache Fengnan Chang
2021-11-26 15:21 ` Chao Yu [this message]
2021-11-26 15:12 ` [f2fs-dev] [PATCH v2 1/2] f2fs: fix remove page failed in invalidate compress pages 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=bc37d799-ae77-9ab7-14a3-a70fccb0d454@kernel.org \
--to=chao@kernel.org \
--cc=changfengnan@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).