The following series implements new feature: ploop push_backup. The idea is to suspend all incoming WRITE-requests until userspace backup application reports explicitly that corresponding parts of ploop block device are "pushed" -- i.e. stored in backup.
To improve latency, the kernel ploop tells userspace about suspended requests. This lets userspace to "push" correspondign parts of device out-of-band. After that, the userspace may tell kernel to re-schedule those requests. https://jira.sw.ru/browse/PSBM-45000 --- Maxim Patlasov (4): ploop: introduce pbd ploop: implement PLOOP_IOC_PUSH_BACKUP_IO ploop: wire push_backup into state-machine ploop: push_backup cleanup drivers/block/ploop/Makefile | 2 drivers/block/ploop/dev.c | 226 +++++++++++++++ drivers/block/ploop/push_backup.c | 564 +++++++++++++++++++++++++++++++++++++ drivers/block/ploop/push_backup.h | 19 + include/linux/ploop/ploop.h | 4 include/linux/ploop/ploop_if.h | 42 +++ 6 files changed, 856 insertions(+), 1 deletion(-) create mode 100644 drivers/block/ploop/push_backup.c create mode 100644 drivers/block/ploop/push_backup.h -- Signature _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
