From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/2 v9] reclaim file-backed pages given POSIX_FADV_NOREUSE
Date: Fri, 21 Feb 2025 02:17:35 +0000 [thread overview]
Message-ID: <174010425541.1545236.6174789060988336403.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250212023518.897942-1-jaegeuk@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 12 Feb 2025 02:31:55 +0000 you wrote:
> This patch series does not add new API, but implements POSIX_FADV_NOREUSE where
> it keeps the page ranges in the f2fs superblock and add a way for users to
> reclaim the pages manually.
>
> Change log from v8:
> - remove new APIs, but use fadvise(POSIX_FADV_NOREUSE)
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: keep POSIX_FADV_NOREUSE ranges
https://git.kernel.org/jaegeuk/f2fs/c/ef0c333cad8d
- [f2fs-dev,2/2] f2fs: add a sysfs entry to reclaim POSIX_FADV_NOREUSE pages
https://git.kernel.org/jaegeuk/f2fs/c/a907f3a68ee2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-21 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 2:31 [PATCH 0/2 v9] reclaim file-backed pages given POSIX_FADV_NOREUSE Jaegeuk Kim
2025-02-12 2:31 ` [PATCH 1/2] f2fs: keep POSIX_FADV_NOREUSE ranges Jaegeuk Kim
2025-02-13 2:14 ` [f2fs-dev] " Chao Yu
2025-02-12 2:31 ` [PATCH 2/2] f2fs: add a sysfs entry to reclaim POSIX_FADV_NOREUSE pages Jaegeuk Kim
2025-02-13 2:15 ` [f2fs-dev] " Chao Yu
2025-02-18 8:26 ` [PATCH 0/2 v9] reclaim file-backed pages given POSIX_FADV_NOREUSE Christoph Hellwig
2025-02-19 9:38 ` Jaegeuk Kim
2025-02-21 2:17 ` patchwork-bot+f2fs [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=174010425541.1545236.6174789060988336403.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@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