From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Akilesh Kailash <akailash@google.com>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: another way to set large folio by remembering inode number
Date: Sat, 18 Apr 2026 09:11:29 +0800 [thread overview]
Message-ID: <7c6f4134-b01c-4ec6-a036-d92c5336839c@kernel.org> (raw)
In-Reply-To: <adhPZxtbZxgU-37v@google.com>
On 4/10/2026 9:16 AM, Jaegeuk Kim via Linux-f2fs-devel wrote:
> enum {
> F2FS_XATTR_FADV_LARGEFOLIO,
> };
>
> unsigned int value = BIT(F2FS_XATTR_FADV_LARGEFOLIO);
>
> 1. setxattr(file, "user.fadvise", &value, sizeof(unsigned int), 0)
> -> register the inode number for large folio
> 2. chmod(0400, file)
> -> make Read-Only
> 3. fsync() && close() && open(READ)
> -> f2fs_iget() with large folio
> 4. open(WRITE), mkwrite on mmap, chmod(WRITE)
> -> return error
> 5. close() and open()
> -> goto #3
> 6. unlink
> -> deregister the inode number
>
> Suggested-by: Akilesh Kailash <akailash@google.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-04-18 1:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:45 [f2fs-dev] [PATCH] f2fs: another way to set large folio by remembering inode number Jaegeuk Kim via Linux-f2fs-devel
2026-04-10 1:16 ` [f2fs-dev] [PATCH v2] " Jaegeuk Kim via Linux-f2fs-devel
2026-04-14 8:02 ` Christoph Hellwig
2026-04-14 8:02 ` [f2fs-dev] " Christoph Hellwig
2026-04-15 16:44 ` Jaegeuk Kim
2026-04-15 16:44 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-04-15 17:15 ` Matthew Wilcox
2026-04-15 17:15 ` [f2fs-dev] " Matthew Wilcox
2026-04-15 22:02 ` Jaegeuk Kim
2026-04-15 22:02 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-04-15 23:49 ` Darrick J. Wong
2026-04-15 23:49 ` [f2fs-dev] " Darrick J. Wong via Linux-f2fs-devel
2026-04-16 1:19 ` Jaegeuk Kim
2026-04-16 1:19 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-04-15 16:41 ` Jaegeuk Kim
2026-04-15 16:41 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-04-17 0:58 ` Chao Yu via Linux-f2fs-devel
2026-04-17 16:54 ` Jaegeuk Kim via Linux-f2fs-devel
2026-04-18 1:08 ` Chao Yu via Linux-f2fs-devel
2026-04-18 1:11 ` Chao Yu via Linux-f2fs-devel [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=7c6f4134-b01c-4ec6-a036-d92c5336839c@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=akailash@google.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.