diff options
author | Tejun Heo <tj@kernel.org> | 2012-01-10 15:08:28 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-01-10 16:30:45 -0800 |
commit | 1ebb7044c9142c67d1d2b04d84010b4810a43fd8 (patch) | |
tree | bfacd21f2aabf0b727d678797e2764d010918f29 /net | |
parent | 0565d317768cc66b13e37184f29d9f270c2886dc (diff) | |
download | linux-1ebb7044c9142c67d1d2b04d84010b4810a43fd8.tar.gz linux-1ebb7044c9142c67d1d2b04d84010b4810a43fd8.tar.bz2 linux-1ebb7044c9142c67d1d2b04d84010b4810a43fd8.zip |
mempool: fix first round failure behavior
mempool modifies gfp_mask so that the backing allocator doesn't try too
hard or trigger warning message when there's pool to fall back on. In
addition, for the first try, it removes __GFP_WAIT and IO, so that it
doesn't trigger reclaim or wait when allocation can be fulfilled from
pool; however, when that allocation fails and pool is empty too, it waits
for the pool to be replenished before retrying.
Allocation which could have succeeded after a bit of reclaim has to wait
on the reserved items and it's not like mempool doesn't retry with
__GFP_WAIT and IO. It just does that *after* someone returns an element,
pointlessly delaying things.
Fix it by retrying immediately if the first round of allocation attempts
w/o __GFP_WAIT and IO fails.
[akpm@linux-foundation.org: shorten the lock hold time]
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions