It seems that we interpreted the question differently. I read it as "what happens if we start a native thread that invokes Python", you read it as "what happens if we start a Python thread from our Python app".
Martin Casado <[EMAIL PROTECTED]> writes: > This is a good question, I actually don't know the answer. However, > since Python threads aren't native threads (Python doesn't offer true > concurrency .. or at least it didn't use to) then I don't see why it > wouldn't work for doing auxiliary functions like you want. I could be > missing something simply tho' > >>>> >>>>> I need to periodically perform an action that is likely to take >>>>> some time. I'm concerned about the performance impact on NOX if my >>>>> application is off doing something for a while -- is it likely to >>>>> block all packet processing? >>>>> >>>> If you write your application in C++, then blocking using the NOX >>>> cooperative threading API will not block packet processing. >>>> Instead, the scheduler will switch to another cooperative thread. >>>> >>>> If you're doing CPU-intensive work, though, that won't trigger >>>> rescheduling. >>>> >>> What would happen if we spawn a Python thread from an app? >>> >> >> NOX doesn't currently initialize or handle Python threading, so >> my guess is that sooner or later all hell would break loose. >> > -- Ben Pfaff Nicira Networks, Inc. _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
