summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorWu Fengguang <fengguang.wu@intel.com>2011-12-02 17:21:33 +0100
committerWu Fengguang <fengguang.wu@intel.com>2011-12-08 03:49:27 +0100
commitc5c6343c4d75f9d3226e05a72e7861e967fc8099 (patch)
treee31d6d748b347314d7ef64fac8f14acc36dfb701 /virt
parentwriteback: comment on the bdi dirty threshold (diff)
downloadlinux-c5c6343c4d75f9d3226e05a72e7861e967fc8099.tar.xz
linux-c5c6343c4d75f9d3226e05a72e7861e967fc8099.zip
writeback: permit through good bdi even when global dirty exceeded
On a system with 1 local mount and 1 NFS mount, if the NFS server becomes not responding when dd to the NFS mount, the NFS dirty pages may exceed the global dirty limit and _every_ task involving writing will be blocked. The whole system appears unresponsive. The workaround is to permit through the bdi's that only has a small number of dirty pages. The number chosen (bdi_stat_error pages) is not enough to enable the local disk to run in optimal throughput, however is enough to make the system responsive on a broken NFS mount. The user can then kill the dirtiers on the NFS mount and increase the global dirty limit to bring up the local disk's throughput. It risks allowing dirty pages to grow much larger than the global dirty limit when there are 1000+ mounts, however that's very unlikely to happen, especially in low memory profiles. Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions