Ayush Ranjan ab9d8455d4 Re-use the same device file inode in tmpfs for overlay whiteout files. ...

When using overlayfs with tmpfs as the upper layer (common case), depending on
the application, a lot of whiteouts can be created. This leads to a lot of
memory allocation because new dentry and inode structs need to be allocated for
each whiteout. With this change, we at least avoid the inode allocations.

This is analogous with what Linux does. See fs/overlayfs/ovl_entry.h:ovl_fs's
field `whiteout` with comment "Shared whiteout cache".

PiperOrigin-RevId: 704897805

2024-12-10 17:11:22 -08:00

..

BUILD

vfs: establish lock ordering for FilesystemImpl.PrependPath

2024-11-14 18:14:27 -08:00

copy_up.go

Add IsDescendant to FilesystemImpl.

2023-10-03 11:57:01 -07:00

directory.go

Re-use the same device file inode in tmpfs for overlay whiteout files.

2024-12-10 17:11:22 -08:00

filesystem.go

Re-use the same device file inode in tmpfs for overlay whiteout files.

2024-12-10 17:11:22 -08:00

overlay.go

overlay: remove dirInoCache entries from RmdirAt()

2024-11-19 17:14:01 -08:00

regular_file.go

Update unimpl.EmitUnimplementedEvent interface to add the syscall number.

2023-03-23 17:01:37 -07:00

save_restore.go

Plumb restore context to load*() methods.

2024-03-08 20:28:02 -08:00