summaryrefslogtreecommitdiffstats
path: root/fs/udf
diff options
context:
space:
mode:
authorVivek Goyal <vgoyal@redhat.com>2020-08-19 18:19:56 -0400
committerMiklos Szeredi <mszeredi@redhat.com>2020-09-10 11:39:23 +0200
commit9a752d18c85ae5da28e4a07d52adfd95eacb2495 (patch)
treec337273c403b887dd2cce079a933ffe85ee71649 /fs/udf
parentd0cfb9dcbca6ebd21ec78ea719b451ea4c22cecf (diff)
downloadlinux-stable-9a752d18c85ae5da28e4a07d52adfd95eacb2495.tar.gz
linux-stable-9a752d18c85ae5da28e4a07d52adfd95eacb2495.tar.bz2
linux-stable-9a752d18c85ae5da28e4a07d52adfd95eacb2495.zip
virtiofs: add logic to free up a memory range
Add logic to free up a busy memory range. Freed memory range will be returned to free pool. Add a worker which can be started to select and free some busy memory ranges. Process can also steal one of its busy dax ranges if free range is not available. I will refer it to as direct reclaim. If free range is not available and nothing can't be stolen from same inode, caller waits on a waitq for free range to become available. For reclaiming a range, as of now we need to hold following locks in specified order. down_write(&fi->i_mmap_sem); down_write(&fi->dax->sem); We look for a free range in following order. A. Try to get a free range. B. If not, try direct reclaim. C. If not, wait for a memory range to become free Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Liu Bo <bo.liu@linux.alibaba.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'fs/udf')
0 files changed, 0 insertions, 0 deletions