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

[Xen-API] task_server.ml

  • To: xen-api@xxxxxxxxxxxxx
  • From: Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx>
  • Date: Thu, 2 Aug 2012 12:44:15 +0200
  • Delivery-date: Thu, 02 Aug 2012 10:44:49 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>


I am wondering why the subtask field is not protected in the function 
with_subtask in xen-api/ocaml/xenops/task_server.ml. It is not clear to me that 
the invariant "only one thread per task" is enforced in xenopsd (where there 
are *a lot* of asynchronous processes) and in the storage layer (ok, there is 
only one call to with_subtask here, and it seems relatively safe as the main 
task is short-lived and not passed around, but how do you ensure it will still 
be enforced in future changes). Is there any good reason to that ?

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.