amd-xgbe: use PAGE_ALLOC_COSTLY_ORDER in xgbe_map_rx_buffer
authorMichal Hocko <mhocko@suse.com>
Fri, 2 Jun 2017 15:54:08 +0000 (17:54 +0200)
committerDavid S. Miller <davem@davemloft.net>
Mon, 5 Jun 2017 00:01:00 +0000 (20:01 -0400)
commita7c0b8bee212e22725196fda8389bff9ade3ac68
treefa43d34a7ac4bf20215d8c46f8db05b178c7ce23
parent5f733ee68f9a4df94775299ac6a7ab260704f6ed
amd-xgbe: use PAGE_ALLOC_COSTLY_ORDER in xgbe_map_rx_buffer

xgbe_map_rx_buffer is rather confused about what PAGE_ALLOC_COSTLY_ORDER
means. It uses PAGE_ALLOC_COSTLY_ORDER-1 assuming that
PAGE_ALLOC_COSTLY_ORDER is the first costly order which is not the case
actually because orders larger than that are costly. And even that
applies only to sleeping allocations which is not the case here. We
simply do not perform any costly operations like reclaim or compaction
for those. Simplify the code by dropping the order calculation and use
PAGE_ALLOC_COSTLY_ORDER directly.

Signed-off-by: Michal Hocko <mhocko@suse.com>
Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/ethernet/amd/xgbe/xgbe-desc.c