diff options
author | Eric Dumazet <edumazet@google.com> | 2014-08-27 20:49:34 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-08-29 20:28:23 -0700 |
commit | d9b2938aabf757da2d40153489b251d4fc3fdd18 (patch) | |
tree | 6916bac985be5ffe9d282a94cd55bf2a754bdf53 /firmware | |
parent | bcc735473c1a0e053a9599af7fdf6a49e513549c (diff) |
net: attempt a single high order allocation
In commit ed98df3361f0 ("net: use __GFP_NORETRY for high order
allocations") we tried to address one issue caused by order-3
allocations.
We still observe high latencies and system overhead in situations where
compaction is not successful.
Instead of trying order-3, order-2, and order-1, do a single order-3
best effort and immediately fallback to plain order-0.
This mimics slub strategy to fallback to slab min order if the high
order allocation used for performance failed.
Order-3 allocations give a performance boost only if they can be done
without recurring and expensive memory scan.
Quoting David :
The page allocator relies on synchronous (sync light) memory compaction
after direct reclaim for allocations that don't retry and deferred
compaction doesn't work with this strategy because the allocation order
is always decreasing from the previous failed attempt.
This means sync light compaction will always be encountered if memory
cannot be defragmented or reclaimed several times during the
skb_page_frag_refill() iteration.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions