From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2 v5] add ioctl/sysfs to donate file-backed pages
Date: Thu, 16 Jan 2025 23:58:19 -0800 [thread overview]
Message-ID: <Z4oNmx2xPkdzvkUd@infradead.org> (raw)
In-Reply-To: <20250116172438.2143971-1-jaegeuk@kernel.org>
Still NAC for sneaking in an almost undocumented MM feature into
a file system ioctl. Especially while a discussion on that is still
ongoin.
And it's still bad that you don't even bother to Cc fsdevel on this,
nor linux-api or in this case the mm list.
On Thu, Jan 16, 2025 at 05:19:42PM +0000, Jaegeuk Kim wrote:
> If users clearly know which file-backed pages to reclaim in system view, they
> can use this ioctl() to register in advance and reclaim all at once later.
>
> Change log from v4:
> - fix range handling
>
> Change log from v3:
> - cover partial range
>
> Change log from v2:
> - add more boundary checks
> - de-register the range, if len is zero
>
> Jaegeuk Kim (1):
> f2fs: add a sysfs entry to request donate file-backed pages
>
> Yi Sun (1):
> f2fs: Optimize f2fs_truncate_data_blocks_range()
>
> Documentation/ABI/testing/sysfs-fs-f2fs | 7 ++++++
> fs/f2fs/f2fs.h | 2 ++
> fs/f2fs/file.c | 29 +++++++++++++++++++++----
> fs/f2fs/shrinker.c | 27 +++++++++++++++++++++++
> fs/f2fs/sysfs.c | 8 +++++++
> 5 files changed, 69 insertions(+), 4 deletions(-)
>
> --
> 2.48.0.rc2.279.g1de40edade-goog
>
>
---end quoted text---
next parent reply other threads:[~2025-01-17 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250116172438.2143971-1-jaegeuk@kernel.org>
2025-01-17 7:58 ` Christoph Hellwig [this message]
2025-01-17 16:40 ` [PATCH 0/2 v5] add ioctl/sysfs to donate file-backed pages Jaegeuk Kim
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=Z4oNmx2xPkdzvkUd@infradead.org \
--to=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox