[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [Qemu-devel] [RFC v4 16/21] blockjobs: add waiting stat

From: Eric Blake
Subject: Re: [Qemu-block] [Qemu-devel] [RFC v4 16/21] blockjobs: add waiting status
Date: Tue, 27 Feb 2018 14:00:05 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 02/23/2018 05:51 PM, John Snow wrote:
For jobs that are stuck waiting on others in a transaction, it would
be nice to know that they are no longer "running" in that sense, but
instead are waiting on other jobs in the transaction.

Jobs that are "waiting" in this sense cannot be meaningfully altered
any longer as they have left their running loop. The only meaningful
user verb for jobs in this state is "cancel," which will cancel the
whole transaction, too.

Running -> Waiting:   Normal transition.
Ready   -> Waiting:   Normal transition.
Waiting -> Aborting:  Transactional cancellation.
Waiting -> Concluded: Normal transition.

Removed Transitions:
Running -> Concluded: Jobs must go to WAITING first.
Ready   -> Concluded: Jobs must go to WAITING fisrt.


+++ b/blockjob.c

@@ -3934,6 +3938,29 @@
              'offset': 'int',
              'speed' : 'int' } }
+# Emitted when a block job that is part of a transction has stopped work and is


+# waiting for other jobs in the transaction to reach the same state.

Is this event emitted only for 'new-style' transactions (old drivers will never see it, because they don't request new style), or always (old drivers will see, but presumably ignore, it)?

Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]