RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-23 18:45:07 +00:00
Code Issues Activity Actions

Kernel: Invalidate file-backed VMO's when inodes are written.

Browse source 
The current strategy is simply to nuke all physical pages and force
reload them from disk. This is obviously not optimal and should eventually
be optimized. It should be fairly straightforward.
This commit is contained in:
Andreas Kling 2019-02-05 08:17:46 +01:00
parent af21a45b1a
commit ca16d9d98e
7 changed files with 117 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

12
Kernel/FileSystem.cpp
View file

@ -109,6 +109,18 @@ void Inode::will_be_destroyed()
flush_metadata();
}
void Inode::inode_contents_changed(off_t offset, size_t size, const byte* data)
{
if (m_vmo)
m_vmo->inode_contents_changed(Badge<Inode>(), offset, size, data);
}
void Inode::inode_size_changed(size_t old_size, size_t new_size)
{
if (m_vmo)
m_vmo->inode_size_changed(Badge<Inode>(), old_size, new_size);
}
int Inode::set_atime(time_t)
{
return -ENOTIMPL;