The commit is pushed to "branch-rh7-3.10.0-327.28.2.vz7.17.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.28.2.vz7.17.2
-->
commit 9c08b7e913cf502ea61ca00814247488bdb1f65f
Author: Vladimir Davydov
Date: Tue Aug 23 17:08:57 2016 +0400
mm: memc
On 08/23/2016 02:38 PM, Vladimir Davydov wrote:
> The new file is supposed to be used for migrating pages accounted to a
> memory cgroup to a particular set of numa nodes. The reason to add it is
> that currently there's no API for migrating unmapped file pages used for
> storing page cache (neit
The new file is supposed to be used for migrating pages accounted to a
memory cgroup to a particular set of numa nodes. The reason to add it is
that currently there's no API for migrating unmapped file pages used for
storing page cache (neither migrate_pages syscall nor cpuset subsys
doesn't provid
On Tue, Aug 23, 2016 at 12:57:53PM +0300, Andrey Ryabinin wrote:
...
> echo "0 100" > /sys/fs/cgroup/memory/machine.slice/100/memory.numa_migrate
>
> [ 296.073002] BUG: soft lockup - CPU#1 stuck for 22s! [bash:4028]
Thanks for catching, will fix in v2.
> > +static struct page *memcg_numa_migrat
On 08/18/2016 03:44 PM, Vladimir Davydov wrote:
> The new file is supposed to be used for migrating pages accounted to a
> memory cgroup to a particular set of numa nodes. The reason to add it is
> that currently there's no API for migrating unmapped file pages used for
> storing page cache (neit
The commit is pushed to "branch-rh7-3.10.0-327.28.2.vz7.17.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.28.2.vz7.17.2
-->
commit 96e55a820e144b35e9254e97cdc0afbb4f879b3f
Author: Vladimir Davydov
Date: Tue Aug 23 13:13:19 2016 +0400
vzprivne
Acked-by: Pavel Tikhomirov
On 08/23/2016 11:46 AM, Vladimir Davydov wrote:
For the sake of Docker, we only call vzprivnet rules if skb comes from
the host [1]. To check that, we look at skb->dev->nd_net->owner_ve. This
works fine when skb is retransmitted by a device (as it is the case in
case
For the sake of Docker, we only call vzprivnet rules if skb comes from
the host [1]. To check that, we look at skb->dev->nd_net->owner_ve. This
works fine when skb is retransmitted by a device (as it is the case in
case of a bridged network), but this results in KP when skb is sent
directly to a ve
