From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu] add revert to work around performance regression when backing up large RBD disk
Date: Thu, 19 May 2022 09:36:44 +0200 [thread overview]
Message-ID: <108103d5-6508-676d-fceb-50b9fbe75d6b@proxmox.com> (raw)
In-Reply-To: <20220517082949.60472-1-f.ebner@proxmox.com>
Am 5/17/22 um 10:29 schrieb Fabian Ebner:
> resulting in QMP timeouts and very slow backups. The plan is to figure
> out (ideally together with upstream) a way to make the implementation
> of bdrv_co_block_status for RBD more efficient. But for now, revert
> the problematic change as a stop-gap measure.
>
> Upstream bug report:
> https://gitlab.com/qemu-project/qemu/-/issues/1026
>
> Forum threads:
> https://forum.proxmox.com/threads/109272/
> https://forum.proxmox.com/threads/109448/
> https://forum.proxmox.com/threads/101334/ (partially)
>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
>
> I simply removed the other two patches already fixing the offending
> commit from the "series" file, to make it less likely that we forget
> to re-add them once we revert the revert and to reduce the git diff.
> Hope that is ok.
>
> ...k-rbd-implement-bdrv_co_block_status.patch | 161 ++++++++++++++++++
> debian/patches/series | 3 +-
> 2 files changed, 162 insertions(+), 2 deletions(-)
> create mode 100644 debian/patches/pve/0053-Revert-block-rbd-implement-bdrv_co_block_status.patch
>
>
applied, thanks!
prev parent reply other threads:[~2022-05-19 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 8:29 [pve-devel] " Fabian Ebner
2022-05-19 7:36 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=108103d5-6508-676d-fceb-50b9fbe75d6b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox