The commit is pushed to "branch-rh9-5.14.0-427.35.1.vz9.76.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.35.1.vz9.76.4
-->
commit b9727d032aeec976764e9896dfe74be34819fd89
Author: Liu Kui
Date: Mon Oct 7 22:59:28 2024 +0800
fs/fuse kio: Add kRPC v
The commit is pushed to "branch-rh9-5.14.0-427.35.1.vz9.76.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.35.1.vz9.76.4
-->
commit 322e97167851f9e72fcf9c76060f0b9639f714f2
Author: Alexey Kuznetsov
Date: Wed Oct 2 02:40:39 2024 +0800
fs: fuse: pcs:
The commit is pushed to "branch-rh9-5.14.0-427.35.1.vz9.76.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.35.1.vz9.76.4
-->
commit a92f22f9e2bfd0465311a4e01d2344a37533cfec
Author: Alexey Kuznetsov
Date: Wed Oct 2 02:47:57 2024 +0800
fs: fuse: pcs:
The commit is pushed to "branch-rh9-5.14.0-427.35.1.vz9.76.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.35.1.vz9.76.4
-->
commit b19114cfb448540828342c074152b4058f29e736
Author: Alexey Kuznetsov
Date: Wed Oct 2 02:44:36 2024 +0800
fs: fuse: pcs:
The commit is pushed to "branch-rh9-5.14.0-427.35.1.vz9.76.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.35.1.vz9.76.4
-->
commit c6c291e4cfa160ec354a2199dfc34b5ea15ec7d1
Author: Liu Kui
Date: Tue Oct 1 13:07:58 2024 +0800
fs/fuse kio: avoid acqu
The commit is pushed to "branch-rh9-5.14.0-427.35.1.vz9.76.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.35.1.vz9.76.4
-->
commit 06e44a360bf5bb5406a4be1172b26d6c195a2422
Author: Liu Kui
Date: Tue Oct 1 13:07:39 2024 +0800
fs/fuse kio: fix krpc s
Prepare to reduce locking by using atomic 32 bit access to the fields.
To ensure this we need to use the _ONCE macros.
https://virtuozzo.atlassian.net/browse/VSTOR-91659
Signed-off-by: Alexander Atanasov
---
drivers/md/dm-ploop-bat.c | 2 +-
drivers/md/dm-ploop-map.c | 18 +-
2
Fix direct bitops to use set_bit/clear_bit which
are atomic - this is required since there are
some places in code that do not use locking when
operating on that bits. this is also a preparation
to relax locking.
https://virtuozzo.atlassian.net/browse/VSTOR-91820
Signed-off-by: Alexander Atanasov
now proper bitops are used for status we do not need to lock.
Signed-off-by: Alexander Atanasov
---
drivers/md/dm-ploop-cmd.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/md/dm-ploop-cmd.c b/drivers/md/dm-ploop-cmd.c
index f10850d801eb..7f68fec834e9 100644
--- a/drivers/md/dm-plo
Convert to lockless lists - intermix with regular list due to
that next pointer in both list_head and llist_head is the first
field, and prev is not used. Do this so we can make babysteps
forward.
Signed-off-by: Alexander Atanasov
---
drivers/md/dm-ploop-bat.c| 3 +--
drivers/md/dm-ploop-ma
Currently lock is taken once for all pios submitted(code block),
move it to protect only the list insertion (data).
The goal is to reduce lock contention on the deferred lock as
it is in the top of lock stats.
Signed-off-by: Alexander Atanasov
---
drivers/md/dm-ploop-map.c | 8
1 file c
Ack
On Mon, Oct 7, 2024 at 11:11 PM Liu Kui wrote:
>
> Replace the module parameter 'pcs_krpc_support' with 'pcs_krpc_version'
> for better kRPC version management. Older userspace client would be able
> to detect version mismatch with absence of 'pcs_krpc_support', while
> newer userspace client
Replace the module parameter 'pcs_krpc_support' with 'pcs_krpc_version'
for better kRPC version management. Older userspace client would be able
to detect version mismatch with absence of 'pcs_krpc_support', while
newer userspace client will check against 'pcs_krpc_version'.
Relates to
https://vir
13 matches
Mail list logo
