qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, armbru@redhat.com, eblake@redhat.com,
	stefanha@redhat.com, hreitz@redhat.com, kwolf@redhat.com,
	vsementsov@virtuozzo.com, jsnow@redhat.com
Subject: [PATCH 0/4] block: copy-before-write: cbw-timeout
Date: Wed,  2 Mar 2022 17:24:38 +0100	[thread overview]
Message-ID: <20220302162442.2052461-1-vsementsov@virtuozzo.com> (raw)

Hi all!

There is another new option, that allows to limit cbw operation by some
timeout.

So, for example, using cbw-timeout=60 and on-cbw-error=break-snapshot
you can be sure that guest write will not stuck for more than 60
seconds.

Based-on: <20220301205929.2006041-1-vsementsov@virtuozzo.com>
   ([PATCH 0/3] block: copy-before-write: on-cbw-error behavior)

Vladimir Sementsov-Ogievskiy (4):
  util: add qemu-co-timeout
  block/block-copy: block_copy(): add timeout_ns parameter
  block/copy-before-write: implement cbw-timeout option
  iotests: copy-before-write: add cases for cbw-timeout option

 qapi/block-core.json                          |  5 +-
 include/block/block-copy.h                    |  2 +-
 include/qemu/coroutine.h                      | 13 +++
 block/block-copy.c                            | 28 ++++--
 block/copy-before-write.c                     |  6 +-
 util/qemu-co-timeout.c                        | 89 +++++++++++++++++++
 tests/qemu-iotests/tests/copy-before-write    | 78 ++++++++++++++++
 .../qemu-iotests/tests/copy-before-write.out  |  4 +-
 util/meson.build                              |  1 +
 9 files changed, 213 insertions(+), 13 deletions(-)
 create mode 100644 util/qemu-co-timeout.c

-- 
2.31.1



             reply	other threads:[~2022-03-02 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 16:24 Vladimir Sementsov-Ogievskiy [this message]
2022-03-02 16:24 ` [PATCH 1/4] util: add qemu-co-timeout Vladimir Sementsov-Ogievskiy
2022-03-02 16:24 ` [PATCH 2/4] block/block-copy: block_copy(): add timeout_ns parameter Vladimir Sementsov-Ogievskiy
2022-03-09 17:35   ` Vladimir Sementsov-Ogievskiy
2022-03-02 16:24 ` [PATCH 3/4] block/copy-before-write: implement cbw-timeout option Vladimir Sementsov-Ogievskiy
2022-03-02 16:24 ` [PATCH 4/4] iotests: copy-before-write: add cases for " Vladimir Sementsov-Ogievskiy

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=20220302162442.2052461-1-vsementsov@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).