tmpfs: add the option to disable swap
Subsystems (2)
cover tmpfs: add the option to disable swap
Many folks suggest using tmpfs is not great because it can use swap. That's not a good reason to *not* use tmpfs, what's just missing is just the option to let you disable it. And so this does that, to enable that and also let users experiment with it.
Reconfiguring is not supported, so what you set up first is what you can keep with regards to swap options. Enabling support to disable on the fly and add swap on the fly *is* possible, but I'm not sure we need that yet.
Matthew -- the first patch just makes it easier to read the second, but it does beg a few questions in it with regards to semantics about the folio and the inode after splitting a huge page so review for that would be greatly appreciated.
To test I've used kdevops [0] 8 vpcu 4 GiB libvirt guest on linux-next.
I'm doing this work as part of future experimentation with tmpfs and the page cache, but given a common complaint found about tmpfs is the innability to work without the page cache I figured this might be useful to others. It would also prove useful if folks ask for patches for future experimentation we are doing.
To see if you hit swap:
mkswap /dev/nvme2n1
swapon /dev/nvme2n1
free -h
With swap - what we see today
=============================
mount -t tmpfs -o size=5G tmpfs /data-tmpfs/
dd if=/dev/urandom of=/data-tmpfs/5g-rand2 bs=1G count=5 free -h
total used free shared buff/cache available
Mem: 3.7Gi 2.6Gi 1.2Gi 2.2Gi 2.2Gi 1.2Gi Swap: 99Gi 2.8Gi 97Gi
Without swap
=============
free -h
total used free shared buff/cache available
Mem: 3.7Gi 387Mi 3.4Gi 2.1Mi 57Mi 3.3Gi Swap: 99Gi 0B 99Gi
mount -t tmpfs -o size=5G -o noswap tmpfs /data-tmpfs/
dd if=/dev/urandom of=/data-tmpfs/5g-rand2 bs=1G count=5 free -h
total used free shared buff/cache available
Mem: 3.7Gi 2.6Gi 1.2Gi 2.3Gi 2.3Gi 1.1Gi Swap: 99Gi 21Mi 99Gi
The mix and match remount testing
=================================
# Cannot disable swap after it was first enabled:
mount -t tmpfs -o size=5G tmpfs /data-tmpfs/
mount -t tmpfs -o remount -o size=5G -o noswap tmpfs /data-tmpfs/
mount: /data-tmpfs: mount point not mounted or bad option.
dmesg(1) may have more information after failed mount system call.
dmesg -c
tmpfs: Cannot disable swap on remount
# Remount with the same noswap option is OK:
mount -t tmpfs -o size=5G -o noswap tmpfs /data-tmpfs/
mount -t tmpfs -o remount -o size=5G -o noswap tmpfs /data-tmpfs/ dmesg -c
# Trying to enable swap with a remount after it first disabled:
mount -t tmpfs -o size=5G -o noswap tmpfs /data-tmpfs/
mount -t tmpfs -o remount -o size=5G tmpfs /data-tmpfs/
mount: /data-tmpfs: mount point not mounted or bad option.
dmesg(1) may have more information after failed mount system call.
dmesg -c
tmpfs: Cannot enable swap on remount if it was disabled on first mount
[0] https://github.com/linux-kdevops/kdevops
Luis Chamberlain (2):
shmem: set shmem_writepage() variables early
shmem: add support to ignore swap
include/linux/shmem_fs.h | 1 + mm/shmem.c | 33 ++++++++++++++++++++++++++++++--- 2 files changed, 31 insertions(+), 3 deletions(-)
Signature · 1 line
2.39.0
RFC 1/2 shmem: set shmem_writepage() variables early
shmem_writepage() sets up variables typically used *after* a possible huge page split. However even if that does happen the address space mapping should not change. So it should be safe to set that from the beginning.
The folio should always be locked from the start as well. It however was not clear if the folio address can / should change, as well as the first inode.
This commit makes no functional changes other a double check on the folio locking which might be superflous. This change should help make the subsequent patch easier to review.
--- mm/shmem.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
mm/shmem.c +5 -3
@@ -1332,11 +1332,13 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc) {struct folio *folio =page_folio (page);struct shmem_inode_info *info; -struct address_space *mapping; -struct inode *inode; +struct address_space *mapping = folio->mapping; +struct inode *inode = mapping->host;swp_entry_t swap;pgoff_t index; +BUG_ON (!folio_test_locked (folio)); +/* * If /sys/kernel/mm/transparent_hugepage/shmem_enabled is "always" or * "force", drivers/gpu/drm/i915/gem/i915_gem_shmem.c gets huge pages,
@@ -1351,8 +1353,8 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)folio_clear_dirty (folio); } +/* Can the folio or first inode change on after a split? */ BUG_ON (!folio_test_locked (folio)); - mapping = folio->mapping; index = folio->index; inode = mapping->host; info =SHMEM_I (inode);
Signature · 1 line
2.39.0
Re: [RFC 1/2] shmem: set shmem_writepage() variables early
Quoted 4 lines · Luis Chamberlain
shmem_writepage()sets up variables typically used *after* a possible huge page split. However even if that does happen the address space mapping should not change. So it should be safe to set that from the beginning.
Yes, we can get mapping from the folio early. It doesn't change on split.
Quoted 7 lines
The folio should always be locked from the start as well. It however was not clear if the folio address can / should change, as well as the first inode.
This commit makes no functional changes other a double check on the folio locking which might be superflous. This change should help make the subsequent patch easier to review.
You don't need to check that the folio's locked, and you don't need to reassign inode after the split.
Quoted 38 lines
Signed-off-by Luis Chamberlain <[email protected]>--- mm/shmem.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)mm/shmem.c +5
-3@@ -1332,11 +1332,13 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc) {struct folio *folio =page_folio (page);struct shmem_inode_info *info; -struct address_space *mapping; -struct inode *inode; +struct address_space *mapping = folio->mapping; +struct inode *inode = mapping->host;swp_entry_t swap;pgoff_t index; +BUG_ON (!folio_test_locked (folio)); +/* * If /sys/kernel/mm/transparent_hugepage/shmem_enabled is "always" or * "force", drivers/gpu/drm/i915/gem/i915_gem_shmem.c gets huge pages, @@ -1351,8 +1353,8 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)folio_clear_dirty (folio); } +/* Can the folio or first inode change on after a split? */ BUG_ON (!folio_test_locked (folio)); - mapping = folio->mapping; index = folio->index; inode = mapping->host; info =SHMEM_I (inode);Signature · 1 line
2.39.0
Re: [RFC 1/2] shmem: set shmem_writepage() variables early
Quoted 8 lines · Matthew Wilcox
Quoted 4 lines · Luis Chamberlain
shmem_writepage()sets up variables typically used *after* a possible huge page split. However even if that does happen the address space mapping should not change. So it should be safe to set that from the beginning.Yes, we can get mapping from the folio early. It doesn't change on split.
Great.
Quoted 9 lines
Quoted 7 lines
The folio should always be locked from the start as well. It however was not clear if the folio address can / should change, as well as the first inode.
This commit makes no functional changes other a double check on the folio locking which might be superflous. This change should help make the subsequent patch easier to review.
You don't need to check that the folio's locked,
That BUG_ON() has been on shmem since linux-history days it's probably best as a separate patch.
Quoted 2 lines
and you don't
need to reassign inode after the split.
Great! Thanks for this confirmation!
Luis
RFC 2/2 shmem: add support to ignore swap
In reply to Luis ChamberlainIn doing experimentations with shmem having the option to avoid becomes a useful mechanism. One of the *raves* about brd over shmem is you can avoid swap, but that's not really a good reason to use brd if we can instead use shmem. Using brd has its own good reasons to exist, but just because "tmpfs" doesn't let you do that is not a great reason to avoid it if we can easily add support for it.
I don't add support for reconfiguring incompatible options, but if we really wanted to we can add support for that.
--- include/linux/shmem_fs.h | 1 + mm/shmem.c | 25 +++++++++++++++++++++++++ 2 files changed, 26 insertions(+)
include/linux/shmem_fs.h +1 -0
@@ -45,6 +45,7 @@ struct shmem_sb_info {kuid_t uid;/* Mount uid for root directory */ kgid_t gid;/* Mount gid for root directory */ bool full_inums;/* If i_ino should be uint or ino_t */ +bool noswap;/* ingores VM relcaim / swap requests */ ino_t next_ino;/* The next per-sb inode number to use */ ino_t __percpu *ino_batch;/* The next per-cpu inode number to use */ struct mempolicy *mpol;/* default memory policy for mappings */
mm/shmem.c +25 -0
@@ -116,10 +116,12 @@ struct shmem_options {bool full_inums;int huge;int seen; +bool noswap;#define SHMEM_SEEN_BLOCKS 1#define SHMEM_SEEN_INODES 2#define SHMEM_SEEN_HUGE 4#define SHMEM_SEEN_INUMS 8 +#define SHMEM_SEEN_NOSWAP 16 };#ifdef CONFIG_TMPFS
@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio)); +if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ; +/* * If /sys/kernel/mm/transparent_hugepage/shmem_enabled is "always" or * "force", drivers/gpu/drm/i915/gem/i915_gem_shmem.c gets huge pages,
@@ -3465,6 +3471,7 @@ enum shmem_param { Opt_uid, Opt_inode32, Opt_inode64, + Opt_noswap, }; static const struct constant_table shmem_param_enums_huge[] = {
@@ -3486,6 +3493,7 @@ const struct fs_parameter_spec shmem_fs_parameters[] = {fsparam_u32 ("uid" , Opt_uid),fsparam_flag ("inode32" , Opt_inode32),fsparam_flag ("inode64" , Opt_inode64), + fsparam_flag ("noswap", Opt_noswap), {} };
@@ -3569,6 +3577,10 @@ static int shmem_parse_one(struct fs_context *fc, struct fs_parameter *param) ctx->full_inums = true; ctx->seen |=SHMEM_SEEN_INUMS ;break ; +case Opt_noswap: + ctx->noswap = true; + ctx->seen |=SHMEM_SEEN_NOSWAP ; +break ; }return 0 ;
@@ -3667,6 +3679,14 @@ static int shmem_reconfigure(struct fs_context *fc) err ="Current inum too high to switch to 32-bit inums" ; goto out; } +if ((ctx->seen &SHMEM_SEEN_NOSWAP ) && ctx->noswap && !sbinfo->noswap) { + err ="Cannot disable swap on remount" ; + goto out; + } +if (!(ctx->seen &SHMEM_SEEN_NOSWAP ) && !ctx->noswap && sbinfo->noswap) { + err ="Cannot enable swap on remount if it was disabled on first mount" ; + goto out; + }if (ctx->seen &SHMEM_SEEN_HUGE ) sbinfo->huge = ctx->huge;
@@ -3687,6 +3707,10 @@ static int shmem_reconfigure(struct fs_context *fc) sbinfo->mpol = ctx->mpol;/* transfers initial ref */ ctx->mpol =NULL ; } + +if (ctx->noswap) + sbinfo->noswap = true; +raw_spin_unlock (&sbinfo->stat_lock);mpol_put (mpol);return 0 ;
@@ -3784,6 +3808,7 @@ static int shmem_fill_super(struct super_block *sb, struct fs_context *fc) ctx->inodes =shmem_default_max_inodes ();if (!(ctx->seen &SHMEM_SEEN_INUMS )) ctx->full_inums =IS_ENABLED (CONFIG_TMPFS_INODE64 ); + sbinfo->noswap = ctx->noswap; }else { sb->s_flags |=SB_NOUSER ; }
Signature · 1 line
2.39.0
Re: [RFC 2/2] shmem: add support to ignore swap
mm/shmem.c static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 12 lines · Luis Chamberlain
mm/shmem.c +3
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio)); +if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ;
Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Re: [RFC 2/2] shmem: add support to ignore swap
Quoted 11 lines · Matthew Wilcox
Quoted 10 lines · Luis Chamberlain
mm/shmem.c +1
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio));
Quoted 7 lines
mm/shmem.c static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 2 lines
mm/shmem.c +2
-0+if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ;Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Ah, makes sense, so in effect then if we do that then on reclaim we should be able to even WARN_ON(sbinfo->noswap) assuming we did everthing right.
Hrm, we have invalidate_mapping_pages(mapping, 0, -1) but that seems a bit too late how about d_mark_dontcache() on shmem_get_inode() instead?
Luis
Re: [RFC 2/2] shmem: add support to ignore swap
Quoted 20 lines · Luis Chamberlain
Quoted 11 lines · Matthew Wilcox
Quoted 10 lines · Luis Chamberlain
mm/shmem.c +1
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio));Quoted 7 lines
mm/shmem.c static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 2 lines
mm/shmem.c +2
-0+if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ;Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Quoted 6 lines
Ah, makes sense, so in effect then if we do that then on reclaim we should be able to even
WARN_ON(sbinfo->noswap)assuming we did everthing right.Hrm, we have
invalidate_mapping_pages(mapping, 0, -1)but that seems a bit too late how aboutd_mark_dontcache()onshmem_get_inode()instead?
I was thinking that the two calls to folio_add_lru() in mm/shmem.c should be conditional on sbinfo->noswap.
Re: [RFC 2/2] shmem: add support to ignore swap
Quoted 26 lines · Matthew Wilcox
Quoted 24 lines · Luis Chamberlain
Quoted 11 lines · Matthew Wilcox
Quoted 10 lines · Luis Chamberlain
mm/shmem.c +1
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio));Quoted 7 lines
mm/shmem.c static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 2 lines
mm/shmem.c +2
-0+if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ;Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Ah, makes sense, so in effect then if we do that then on reclaim we should be able to even
WARN_ON(sbinfo->noswap)assuming we did everthing right.
Quoted 6 lines
Quoted 2 lines
Hrm, we have
invalidate_mapping_pages(mapping, 0, -1)but that seems a bit too late how aboutd_mark_dontcache()onshmem_get_inode()instead?I was thinking that the two calls to
folio_add_lru()inmm/shmem.cshould be conditional onsbinfo->noswap.
Wouldn't this cause the folio to not show up in any lru lists, even the unevictable one, which may be a strange discrepancy?
Perhaps we can do something like shmem_lock(), which calls mapping_set_unevictable(), which will make folio_evictable() return true and the LRUs code will take care of the rest?
Re: [RFC 2/2] shmem: add support to ignore swap
Quoted 34 lines · Yosry Ahmed
Quoted 26 lines · Matthew Wilcox
Quoted 24 lines · Luis Chamberlain
Quoted 11 lines · Matthew Wilcox
Quoted 10 lines · Luis Chamberlain
mm/shmem.c +1
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio));Quoted 7 lines
mm/shmem.c static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 2 lines
mm/shmem.c +2
-0+if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ;Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Ah, makes sense, so in effect then if we do that then on reclaim we should be able to even
WARN_ON(sbinfo->noswap)assuming we did everthing right.Quoted 6 lines
Quoted 2 lines
Hrm, we have
invalidate_mapping_pages(mapping, 0, -1)but that seems a bit too late how aboutd_mark_dontcache()onshmem_get_inode()instead?I was thinking that the two calls to
folio_add_lru()inmm/shmem.cshould be conditional onsbinfo->noswap.
Quoted 6 lines
Wouldn't this cause the folio to not show up in any lru lists, even the unevictable one, which may be a strange discrepancy?
Perhaps we can do something like
shmem_lock(), which callsmapping_set_unevictable(), which will makefolio_evictable()return true and the LRUs code will take care of the rest?
If shmem_lock() should take care of that is that because writepages() should not happen or because we have that info->flags & VM_LOCKED stop gap on writepages()? If the earlier then shouldn't we WARN_ON_ONCE() if writepages() is called on info->flags & VM_LOCKED?
While I see the value in mapping_set_unevictable() I am not sure I see the point in using shmem_lock(). I don't see why we should constrain noswap tmpfs option to RLIMIT_MEMLOCK
Please correct me if I'm wrong but the limit seem to be designed for files / IPC / unprivileged perf limits. On the contrary, we'd bump the count for each new inode. Using shmem_lock() would also complicate the inode allocation on shmem as we'd have to unwind on failure from the user_shm_lock(). It would also beg the question of when to capture a ucount for an inode, should we just share one for the superblock at shmem_fill_super() or do we really need to capture it at every single inode creation? In theory we could end up with different limits.
So why not just use mapping_set_unevictable() alone for this use case?
Luis
Re: [RFC 2/2] shmem: add support to ignore swap
Quoted 61 lines · Luis Chamberlain
Quoted 34 lines · Yosry Ahmed
Quoted 26 lines · Matthew Wilcox
Quoted 24 lines · Luis Chamberlain
Quoted 11 lines · Matthew Wilcox
Quoted 10 lines · Luis Chamberlain
mm/shmem.c +1
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)struct shmem_inode_info *info;struct address_space *mapping = folio->mapping;struct inode *inode = mapping->host; +struct shmem_sb_info *sbinfo =SHMEM_SB (inode->i_sb);swp_entry_t swap;pgoff_t index;BUG_ON (!folio_test_locked (folio));Quoted 7 lines
mm/shmem.c static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 2 lines
mm/shmem.c +2
-0+if (wbc->for_reclaim &&unlikely (sbinfo->noswap)) +return AOP_WRITEPAGE_ACTIVATE ;Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Ah, makes sense, so in effect then if we do that then on reclaim we should be able to even
WARN_ON(sbinfo->noswap)assuming we did everthing right.Quoted 6 lines
Quoted 2 lines
Hrm, we have
invalidate_mapping_pages(mapping, 0, -1)but that seems a bit too late how aboutd_mark_dontcache()onshmem_get_inode()instead?I was thinking that the two calls to
folio_add_lru()inmm/shmem.cshould be conditional onsbinfo->noswap.Quoted 6 lines
Wouldn't this cause the folio to not show up in any lru lists, even the unevictable one, which may be a strange discrepancy?
Perhaps we can do something like
shmem_lock(), which callsmapping_set_unevictable(), which will makefolio_evictable()return true and the LRUs code will take care of the rest?If
shmem_lock()should take care of that is that becausewritepages()should not happen or because we have thatinfo->flags&VM_LOCKEDstop gap onwritepages()? If the earlier then shouldn't weWARN_ON_ONCE()ifwritepages()is called oninfo->flags&VM_LOCKED?While I see the value in
mapping_set_unevictable()I am not sure I see the point in usingshmem_lock(). I don't see why we should constrain noswap tmpfs option toRLIMIT_MEMLOCKPlease correct me if I'm wrong but the limit seem to be designed for files / IPC / unprivileged perf limits. On the contrary, we'd bump the count for each new inode. Using
shmem_lock()would also complicate the inode allocation on shmem as we'd have to unwind on failure from theuser_shm_lock(). It would also beg the question of when to capture a ucount for an inode, should we just share one for the superblock atshmem_fill_super()or do we really need to capture it at every single inode creation? In theory we could end up with different limits.
Quoted 1 line
So why not just use
mapping_set_unevictable()alone for this use case?
Sorry if I wasn't clear, I did NOT mean that we should use shmem_lock(), I meant that we do something similar to what shmem_lock() does and use mapping_set_unevictable() or similar.
I think we just need to make sure that if we use mapping_set_unevictable() does not imply that shmem_lock() was used (i.e no code assumes that if the shmem mapping is unevictable then shmem_lock() was used).
Anyway, I am not very knowledgeable here so take anything I say with a grain of salt.
Thanks.
Quoted 2 lines
Luis
Re: [RFC 2/2] shmem: add support to ignore swap
Quoted 62 lines · Yosry Ahmed
Quoted 61 lines · Luis Chamberlain
Quoted 34 lines · Yosry Ahmed
Quoted 26 lines · Matthew Wilcox
Quoted 24 lines · Luis Chamberlain
Quoted 11 lines · Matthew Wilcox
Quoted 10 lines · Luis Chamberlain
(quoted diff) +1
-0@@ -1334,11 +1336,15 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc) struct shmem_inode_info *info; struct address_space *mapping = folio->mapping; struct inode *inode = mapping->host; + struct shmem_sb_info *sbinfo = SHMEM_SB(inode->i_sb); swp_entry_t swap; pgoff_t index; BUG_ON(!folio_test_locked(folio));Quoted 7 lines
Review static int shmem_writepage(struct page *page, struct writeback_control *wbc) · line 1346
Quoted 2 lines
(quoted diff) +2
-0+ if (wbc->for_reclaim && unlikely(sbinfo->noswap)) + return AOP_WRITEPAGE_ACTIVATE;Not sure this is the best way to handle this. We'll still incur the oevrhead of tracking shmem pages on the LRU, only to fail to write them out when the VM thinks we should get rid of them. We'd be better off not putting them on the LRU in the first place.
Ah, makes sense, so in effect then if we do that then on reclaim we should be able to even
WARN_ON(sbinfo->noswap)assuming we did everthing right.Quoted 6 lines
Quoted 2 lines
Hrm, we have
invalidate_mapping_pages(mapping, 0, -1)but that seems a bit too late how aboutd_mark_dontcache()onshmem_get_inode()instead?I was thinking that the two calls to
folio_add_lru()inmm/shmem.cshould be conditional onsbinfo->noswap.Quoted 6 lines
Wouldn't this cause the folio to not show up in any lru lists, even the unevictable one, which may be a strange discrepancy?
Perhaps we can do something like
shmem_lock(), which callsmapping_set_unevictable(), which will makefolio_evictable()return true and the LRUs code will take care of the rest?If
shmem_lock()should take care of that is that becausewritepages()should not happen or because we have thatinfo->flags&VM_LOCKEDstop gap onwritepages()? If the earlier then shouldn't weWARN_ON_ONCE()ifwritepages()is called oninfo->flags&VM_LOCKED?While I see the value in
mapping_set_unevictable()I am not sure I see the point in usingshmem_lock(). I don't see why we should constrain noswap tmpfs option toRLIMIT_MEMLOCKPlease correct me if I'm wrong but the limit seem to be designed for files / IPC / unprivileged perf limits. On the contrary, we'd bump the count for each new inode. Using
shmem_lock()would also complicate the inode allocation on shmem as we'd have to unwind on failure from theuser_shm_lock(). It would also beg the question of when to capture a ucount for an inode, should we just share one for the superblock atshmem_fill_super()or do we really need to capture it at every single inode creation? In theory we could end up with different limits.
Quoted 5 lines
Quoted 1 line
So why not just use
mapping_set_unevictable()alone for this use case?Sorry if I wasn't clear, I did NOT mean that we should use
shmem_lock(), I meant that we do something similar to whatshmem_lock()does and usemapping_set_unevictable()or similar.
Ah OK! Sure yeah I reviewed shmem_lock() usage and I don't think it and its rtlimit baggage makes sense here so the only thing to do is just mapping_set_unevictable().
Quoted 4 lines
I think we just need to make sure that if we use
mapping_set_unevictable()does not imply thatshmem_lock()was used (i.e no code assumes that if the shmem mapping is unevictable thenshmem_lock()was used).
The *other* stuff that shmem_lock() does is rlimit rlimit related to RLIMIT_MEMLOCK, I can't think off hand why we'd confuse the two use cases at the moment, but I'll give it another good luck with this in mind.
I'll test what I have and post a v2 with the feedback received.
Thanks,
Luis