diff options
author | Eric Dumazet <edumazet@google.com> | 2016-10-05 19:13:18 (GMT) |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-10-07 00:53:13 (GMT) |
commit | d35c99ff77ecb2eb239731b799386f3b3637a31e (patch) | |
tree | 35c9a4b47ffd67aa85672dca5bd84d6c83e7a8df /firmware | |
parent | 6664498280cf17a59c3e7cf1a931444c02633ed1 (diff) | |
download | linux-d35c99ff77ecb2eb239731b799386f3b3637a31e.tar.xz |
netlink: do not enter direct reclaim from netlink_dump()
Since linux-3.15, netlink_dump() can use up to 16384 bytes skb
allocations.
Due to struct skb_shared_info ~320 bytes overhead, we end up using
order-3 (on x86) page allocations, that might trigger direct reclaim and
add stress.
The intent was really to attempt a large allocation but immediately
fallback to a smaller one (order-1 on x86) in case of memory stress.
On recent kernels (linux-4.4), we can remove __GFP_DIRECT_RECLAIM to
meet the goal. Old kernels would need to remove __GFP_WAIT
While we are at it, since we do an order-3 allocation, allow to use
all the allocated bytes instead of 16384 to reduce syscalls during
large dumps.
iproute2 already uses 32KB recvmsg() buffer sizes.
Alexei provided an initial patch downsizing to SKB_WITH_OVERHEAD(16384)
Fixes: 9063e21fb026 ("netlink: autosize skb lengthes")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reported-by: Alexei Starovoitov <ast@kernel.org>
Cc: Greg Thelen <gthelen@google.com>
Reviewed-by: Greg Rose <grose@lightfleet.com>
Acked-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions