This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 456] New: Xenstored could help with serialisation

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 456] New: Xenstored could help with serialisation
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 15 Dec 2005 14:04:02 +0000
Delivery-date: Thu, 15 Dec 2005 14:07:49 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Xenstored could help with serialisation
           Product: Xen
           Version: 3.0.0
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ewan@xxxxxxxxxxxxx

At the moment, we have to jump through hoops to serialise critical sections of 
the hotplug scripts.  Xenstored has full transaction support already, so it 
would not be difficult to add "claim lock" and "release lock" calls into 
Xenstored.  This would be a useful addition, saving complicated code at the 
hotplug level, and presumably more widely useful too.

Xenstored would have to include protection in case the holder of the lock dies. 
Perhaps it would suffice for the lock to be associated with a pid, and then if 
the process with that pid is dead when someone else wants the lock, Xenstored 
would steal it on their behalf.  This pid would have to be passed through the 
command line tools, because of course when running bash scripts, the pid 
executing the actual lock command is not necessarily the controlling process.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 456] New: Xenstored could help with serialisation, bugzilla-daemon <=