 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Xenbus watch firing over and over
| To: | Ewan Mellor <ewan@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Xenbus watch firing over and over |
| From: | Jacob Gorm Hansen <jacobg@xxxxxxx> |
| Date: | Thu, 04 Jan 2007 13:18:32 +0100 |
| Cc: | xen-devel <Xen-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Thu, 04 Jan 2007 04:18:31 -0800 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding:sender; b=IGKZhoaQZ+oHtOpA7TITpnWFg8aIPUS5sHMXog8QEQHJCDWe4RCV9NSa3y9gX2Koh1aDMw6W6/re+tGkRUCxEtrotkw61GBQdiU5jJhF+3747Saxhmil6xKa+mWV9/6lIhxwbV5wK50OPI80gP7MyaT60lFuNZjPdHQAAwQktvw= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20070103182539.GA26642@xxxxxxxxxxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <1167848163.2591.5.camel@xxxxxxxxxxxxxxxxxxxxx> <20070103182539.GA26642@xxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Wed, 2007-01-03 at 18:25 +0000, Ewan Mellor wrote: > As far as xenstored is concerned, someone is explicitly deleting and > reregistering that watch -- I don't think this is a bug in xenstored. > You > should expect to receive a watch event as soon as a watch is > registered -- it > looks to me like someone is receiving that event, then unwatching the > node, > reading its value, and reregistering the watch. That explains it, I was trying a simple single-threaded setup where the watch is unregistered once it has fired. What is the rationale for triggering the watch on registration? Jacob _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Christoph Egger |
|---|---|
| Next by Date: | Re: [Xen-devel] Xenbus watch firing over and over, Ewan Mellor |
| Previous by Thread: | Re: [Xen-devel] Xenbus watch firing over and over, Ewan Mellor |
| Next by Thread: | Re: [Xen-devel] Xenbus watch firing over and over, Ewan Mellor |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
