Driver level locking of port driver

[Sergei Fomin]

Hello.

The second decade of the XXI century began recently, but some linked-in 
drivers haven't made use of 4-cores monsters yet. :)

Here is my question.
Suppose I've an erlang VM (R14B02) with several scheduler threads. One 
of the threads enters linked-in driver which has driver level locking. 
At the same moment another thread wants to run driver code for a 
different port process.
Would this thread:
* be locked until the first one frees the driver;
* detect the lock and re-schedule the port process;
* do anything else?


-- 
Sergei Fomin