All of lore.kernel.org
 help / color / mirror / Atom feed
From: Euan Harris <euan.harris@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Dave Scott <Dave.Scott@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: Cancelling asynchronous operations in libxl
Date: Wed, 28 Jan 2015 16:13:44 +0000	[thread overview]
Message-ID: <20150128161342.GA32398@citrix.com> (raw)
In-Reply-To: <21694.33920.188447.567330@mariner.uk.xensource.com>

Hi,

On Tue, Jan 20, 2015 at 04:38:24PM +0000, Ian Jackson wrote:
>  * Is an API along these lines going to meet your needs ?

The API you propose for libxl_ao_cancel, as described in the comment in
libxl.h, looks reasonable to us.    The comment for ERROR_NOTIMPLEMENTED
is a bit confusing: under what circumstances might a task actually be
cancelled although libxl_ao_cancel returned ERROR_NOTIMPLEMENTED?

>  * Can you help me test it ?  Trying to test this in xl is going to be
>    awkward and involve a lot of extraneous and very complicated signal
>    handling; and AFAIAA libvirt doesn't have any cancellation
>    facility.

Yes, of course.   However, wouldn't it also be useful for xl to gain
the ability to cancel long-running operations by handling SIGINT?

>  * Any further comments (eg, re timescales etc).

None that we can think of at the moment.

Thanks,
Euan

  reply	other threads:[~2015-01-28 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 13:50 Cancelling asynchronous operations in libxl Dave Scott
2015-01-20 16:38 ` Ian Jackson
2015-01-28 16:13   ` Euan Harris [this message]
2015-01-28 16:57     ` Ian Jackson
2015-02-02 17:43       ` Ian Jackson
2015-02-03  9:59         ` Euan Harris
2015-02-03 12:04           ` Ian Jackson
2015-06-24 15:33       ` Euan Harris
2015-06-24 15:41         ` Ian Jackson
2015-06-25 10:40           ` Ian Campbell

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=20150128161342.GA32398@citrix.com \
    --to=euan.harris@citrix.com \
    --cc=Dave.Scott@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.