dma_generic_alloc_coherent() requires physically contiguous memory,
hence there is no point in warning about high-order since we can't
do anything about it:
WARNING: CPU: 2 PID: 2072 at mm/page_alloc.c:3530
__alloc_pages_nodemask+0x311/0x610
order 3 >= 3, gfp 0x80d0
Call Trace:
dump_stack+0x19/
The commit is pushed to "branch-rh7-3.10.0-957.1.3.vz7.83.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-957.1.3.vz7.83.11
-->
commit 1bbcb753b7f965b35c68312b11dfaa4ca65b9ed3
Author: Konstantin Khorenko
Date: Fri Feb 8 14:00:11 2019 +0300
mm: all
On 2/8/19 2:19 PM, Konstantin Khorenko wrote:
> If we generate a lot of kmem (dentries and inodes in particular)
> we may hit cgroup kmem limit in GFP_NOFS context (e.g. in
> ext4_alloc_inode()) and fail to free reclaimable inodes due to NOFS
> context.
>
> Detect reclaimable kmem on hitting th
The commit is pushed to "branch-rh7-3.10.0-957.1.3.vz7.83.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-957.1.3.vz7.83.11
-->
commit 1bbb4f5de6b5103929328e82e96091be0cf8b37b
Author: Jiang Biao
Date: Mon Feb 11 17:40:31 2019 +0300
ms/virtio_ballo