Maxim Patlasov writes:
> The commit ec1eeb868 (May 22 2015) ported "separate queue for discard bio"
> patch from RHEL6-based kernel incorrectly. Original patch stated clearly
> that if we want to decrement bio_discard_qlen, bio_qlen must not change:
>
> @@ -500,7 +502,7 @@ ploop_bio_queue(struct
Maxim Patlasov writes:
> It's useless to check for preq->req_rw & REQ_FUA after:
> preq->req_rw &= ~REQ_FUA;
ACK :) But in order to make it clear for others let's post original code
here!
...
preq->req_rw &= ~REQ_FUA;
/* Convert requested fua to fsync */
if (test_and_cle
The commit is pushed to "branch-rh7-3.10.0-327.18.2.vz7.14.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.18.2.vz7.14.15
-->
commit 6504a698d0cb68644ad61f139e528c7fb605a246
Author: Cyrill Gorcunov
Date: Fri Jun 17 13:06:56 2016 +0400
ve/secur
The commit is pushed to "branch-rh7-3.10.0-327.18.2.vz7.14.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.18.2.vz7.14.15
-->
commit 3c080800a7f1d1a3102c9d9de1b46b80e0fec187
Author: Andrey Ryabinin
Date: Fri Jun 17 13:08:24 2016 +0400
ve/devic
The commit is pushed to "branch-rh7-3.10.0-327.18.2.vz7.14.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.18.2.vz7.14.15
-->
commit 32eb6c887fd633b840453f9011a62d8253ef689c
Author: Andrey Ryabinin
Date: Fri Jun 17 13:26:15 2016 +0400
ve/devic
The commit is pushed to "branch-rh7-3.10.0-327.18.2.vz7.14.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.18.2.vz7.14.15
-->
commit 6cf1b457fb7252f4d2ada14f8cff0d3b91c26b5d
Author: Maxim Patlasov
Date: Fri Jun 17 13:32:34 2016 +0400
ploop: fi
The commit is pushed to "branch-rh7-3.10.0-327.18.2.vz7.14.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.18.2.vz7.14.15
-->
commit 75347fcbd30151977601d819a56f0a0bb57182f5
Author: Maxim Patlasov
Date: Fri Jun 17 13:32:34 2016 +0400
ploop: io
Kirill, please review.
--
Best regards,
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
On 06/17/2016 01:35 PM, Vladimir Davydov wrote:
When a cgroup is destroyed, all user memory pages get recharged to the
parent cgroup. Recharging is done by mem_cgroup_reparent_charges which
keeps looping u
When a cgroup is destroyed, all user memory pages get recharged to the
parent cgroup. Recharging is done by mem_cgroup_reparent_charges which
keeps looping until res <= kmem. This is supposed to guarantee that by
the time cgroup gets released, no pages is charged to it. However, the
guarantee might
Changelog:
OpenVZ kernel rh7-3.10.0-327.18.2.vz7.14.16
* sysctl: dropped unused fs.ve-area-access-check, net.ipv4.tcp_max_tw*
* device_cgroup: allow to manage devices from inside a Container in
@pseudosuper state with no usual Container constraints.
This is used on CRIU restore stage.
* devic
___
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
From: Vasily Averin
This patch fixes 25-sec delay on login into systemd based containers.
Userspace application can set timer for past
and expect that the timer will be expired immediately.
This can do not work as expected inside migrated containers.
Translated argument provided to timer can be
12 matches
Mail list logo
