From mboxrd@z Thu Jan 1 00:00:00 1970 From: Euan Harris Subject: Re: [RFC PATCH v2 00/29] libxl: Cancelling asynchronous operations Date: Tue, 14 Apr 2015 10:43:54 +0100 Message-ID: <20150414094354.GE22365@citrix.com> References: <1423599016-32639-1-git-send-email-ian.jackson@eu.citrix.com> <20150218161035.GA4022@citrix.com> <20150407170842.GD3099@citrix.com> <21796.4536.722643.245763@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <21796.4536.722643.245763@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xensource.com, james.bulpin@citrix.com List-Id: xen-devel@lists.xenproject.org On Tue, Apr 07, 2015 at 06:19:52PM +0100, Ian Jackson wrote: > I also mentioned that you counting invocations of > libxl__ao_cancellable_register is less than ideal because it is very > coarse-grained. Yes. A nice feature of counting calls to libxl__ao_cancellable_register is that it is closely tied to identifiable points in the lifetime of the cancellable operation. However for better resolution we could count event-loop iterations since a registration call, or any other easily identifiable point. Thanks, Euan