shmem-move-reclaim-check-early-on-writepages.patch removed from -mm tree
The quilt patch titled
Subject: shmem: move reclaim check early on writepages()
has been removed from the -mm tree. Its filename was
shmem-move-reclaim-check-early-on-writepages.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Luis Chamberlain <[email protected]>
Subject: shmem: move reclaim check early on writepages()
Date: Thu, 9 Mar 2023 15:05:42 -0800
i915_gem requires huge folios to be split when swapping. However we have check for usage of writepages() to ensure it used only for swap purposes later. Avoid the splits if we're not being called for reclaim, even if they should in theory not happen.
This makes the conditions easier to follow on shem_writepage().
---
mm/shmem.c | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-)
mm/shmem.c renamed from mm/shmem.c~shmem-move-reclaim-check-early-on-writepages +10 -12
@@ -1348,6 +1348,16 @@ static int shmem_writepage(struct page *pgoff_t index;/* +* Our capabilities prevent regular writeback or sync from ever calling +* shmem_writepage; but a stacking filesystem might use ->writepage of +* its underlying filesystem, in which case tmpfs should write out to +* swap only in response to memory pressure, and not for the writeback +* threads or sync. +*/ +if (WARN_ON_ONCE (!wbc->for_reclaim)) + goto redirty; + +/* * If /sys/kernel/mm/transparent_hugepage/shmem_enabled is "always" or * "force", drivers/gpu/drm/i915/gem/i915_gem_shmem.c gets huge pages, * and its shmem_writeback() needs them to be split when swapping.
@@ -1368,18 +1378,6 @@ static int shmem_writepage(struct page * goto redirty;/* -* Our capabilities prevent regular writeback or sync from ever calling -* shmem_writepage; but a stacking filesystem might use ->writepage of -* its underlying filesystem, in which case tmpfs should write out to -* swap only in response to memory pressure, and not for the writeback -* threads or sync. -*/ -if (!wbc->for_reclaim) { -WARN_ON_ONCE (1 );/* Still happens? Tell us about it! */ - goto redirty; - } - -/* * This is somewhat ridiculous, but without plumbing a SWAP_MAP_FALLOC * value into swapfile.c, the only way we can correctly account for a * fallocated folio arriving here is now to initialize it and write it.
_
Patches currently in -mm which might be from [email protected] are