diff options
author | Dave Chinner <dchinner@redhat.com> | 2014-06-06 15:59:59 +1000 |
---|---|---|
committer | Dave Chinner <david@fromorbit.com> | 2014-06-06 15:59:59 +1000 |
commit | 1f6d64829db78a7e1d63e15c9f48f0a5d2b5a679 (patch) | |
tree | aa4692eeb903340f84953001667e5c03c53d309c /fs/xfs/xfs_mount.c | |
parent | d6d211db37e75de2ddc3a4f979038c40df7cc79c (diff) | |
download | op-kernel-dev-1f6d64829db78a7e1d63e15c9f48f0a5d2b5a679.zip op-kernel-dev-1f6d64829db78a7e1d63e15c9f48f0a5d2b5a679.tar.gz |
xfs: block allocation work needs to be kswapd aware
Upon memory pressure, kswapd calls xfs_vm_writepage() from
shrink_page_list(). This can result in delayed allocation occurring
and that gets deferred to the the allocation workqueue.
The allocation then runs outside kswapd context, which means if it
needs memory (and it does to demand page metadata from disk) it can
block in shrink_inactive_list() waiting for IO congestion. These
blocking waits are normally avoiding in kswapd context, so under
memory pressure writeback from kswapd can be arbitrarily delayed by
memory reclaim.
To avoid this, pass the kswapd context to the allocation being done
by the workqueue, so that memory reclaim understands correctly that
the work is being done for kswapd and therefore it is not blocked
and does not delay memory reclaim.
To avoid issues with int->char conversion of flag fields (as noticed
in v1 of this patch) convert the flag fields in the struct
xfs_bmalloca to bool types. pahole indicates these variables are
still single byte variables, so no extra space is consumed by this
change.
cc: <stable@vger.kernel.org>
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'fs/xfs/xfs_mount.c')
0 files changed, 0 insertions, 0 deletions