The commit is pushed to "branch-rh7-3.10.0-693.21.1.vz7.46.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-693.21.1.vz7.46.5
-->
commit 98ec64d9082be9d0b5594a0ecd98021fa995ba82
Author: Konstantin Khorenko
Date: Fri Apr 13 19:22:22 2018 +0300
ext4:
The commit is pushed to "branch-rh7-3.10.0-693.21.1.vz7.46.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-693.21.1.vz7.46.5
-->
commit 4a45bc07cbf78806045c5b19bf6e2652ce000d23
Author: Jan Kara
Date: Fri Apr 13 19:22:21 2018 +0300
ms/ext4: move ha
The commit is pushed to "branch-rh7-3.10.0-693.21.1.vz7.46.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-693.21.1.vz7.46.5
-->
commit e92c4dde4105d1f583f5d83f5c29e08f21f00203
Author: Waiman Long
Date: Fri Apr 13 19:22:22 2018 +0300
ext4: Make ca
The commit is pushed to "branch-rh7-3.10.0-693.21.1.vz7.46.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-693.21.1.vz7.46.5
-->
commit 9cdd731a629a0c83ae8864759944aa62d9c8bd5b
Author: Kirill Tkhai
Date: Fri Apr 13 19:18:44 2018 +0300
net: Change
Mainstream has NETLINK_EXT_ACK 11, which is used by fresh
iproute utils. We don't want these utils switch the socket
in repair mode.
https://jira.sw.ru/browse/PSBM-83415
Signed-off-by: Kirill Tkhai
---
include/uapi/linux/netlink.h |3 ++-
net/netlink/af_netlink.c |2 +-
net/netlink/
Konstantin Khorenko writes:
> We faced a situation when all (32) cpus on a node content on sbi->s_es_lock
> shrinking extents on a single superblock and
> shrinking extents goes very slow (180 sec in average!).
>
> crash> struct ext4_sb_info 0x882fcb7ca800 -p
>
> s_es_nr_inode = 3173832,
>
From: Waiman Long
This patch changes the es_stats_cache_hits and es_stats_cache_misses
statistics counts to percpu counters to reduce cacheline contention
issues whem multiple threads are trying to update those counts
simultaneously.
With a 38-threads fio I/O test with 2 shared files (on DAX-mou
If there are several shrinkers working on a single sbi there can be easily a
situation when a neighbor shrinkers reclaimed a bunch of extents and thus a
bunch inoes from the s_es_list but we don't honor this and iterate over
sbi->s_es_list the number of times equal to the initial number of inodes i
From: Jan Kara
Currently callers adding extents to extent status tree were responsible
for adding the inode to the list of inodes with freeable extents. This
is error prone and puts list handling in unnecessarily many places.
Just add inode to the list automatically when the first non-delay exte
We faced a situation when all (32) cpus on a node content on sbi->s_es_lock
shrinking extents on a single superblock and
shrinking extents goes very slow (180 sec in average!).
crash> struct ext4_sb_info 0x882fcb7ca800 -p
s_es_nr_inode = 3173832,
s_es_stats = {
es_stats_shrunk = 70,
10 matches
Mail list logo