If an application does a sequence of (1) big write, (2) little write
we don't necessarily want to reset the size hint based on the smaller
size. The fact that they did any big writes implies they may do more,
and therefore we should try to allocate bigger block reservations, even
if the last few
Before this patch, whenever a struct file (opened to allow writes) was
closed, the multi-block reservation structure associated with the inode
was deleted. That's a problem, especially when there are multiple writers.
Applications that do open-write-close will suffer from greater levels
of
Hi,
On October 8, I posted a GFS2 patch that greatly reduced inter-node
contention for resource group glocks. The patch was called:
GFS2: Set of distributed preferences for rgrps. It implemented a
new scheme whereby each node in a cluster tries to keep to itself
for allocations. This is not
This patch tries to use the journal numbers to evenly distribute
which node prefers which resource group for block allocations. This
is to help performance.
---
fs/gfs2/incore.h | 2 ++
fs/gfs2/lock_dlm.c | 2 ++
fs/gfs2/ops_fstype.c | 1 +
fs/gfs2/rgrp.c | 66
