mirror of
https://github.com/torvalds/linux.git
synced 2024-11-24 21:21:41 +00:00
xfs: revert AIL TASK_KILLABLE threshold
In commit9adf40249e
, we changed the behavior of the AIL thread to set its own task state to KILLABLE whenever the timeout value is nonzero. Unfortunately, this missed the fact that xfsaild_push will return 50ms (aka a longish sleep) when we reach the push target or the AIL becomes empty, so xfsaild goes to sleep for a long period of time in uninterruptible D state. This results in artificially high load averages because KILLABLE processes are UNINTERRUPTIBLE, which contributes to load average even though the AIL is asleep waiting for someone to interrupt it. It's not blocked on IOs or anything, but people scrap ps for processes that look like they're stuck in D state, so restore the previous threshold. Fixes:9adf40249e
("xfs: AIL doesn't need manual pushing") Signed-off-by: Darrick J. Wong <djwong@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
This commit is contained in:
parent
73c34b0b85
commit
04d6dbb553
@ -644,7 +644,12 @@ xfsaild(
|
||||
set_freezable();
|
||||
|
||||
while (1) {
|
||||
if (tout)
|
||||
/*
|
||||
* Long waits of 50ms or more occur when we've run out of items
|
||||
* to push, so we only want uninterruptible state if we're
|
||||
* actually blocked on something.
|
||||
*/
|
||||
if (tout && tout <= 20)
|
||||
set_current_state(TASK_KILLABLE|TASK_FREEZABLE);
|
||||
else
|
||||
set_current_state(TASK_INTERRUPTIBLE|TASK_FREEZABLE);
|
||||
|
Loading…
Reference in New Issue
Block a user