[erlang-questions] Linked-in drivers: driver_lock_driver and driver_create_port
Sat Dec 15 16:25:13 CET 2007
driver_create_port was added to simplify the SMP implementation.
Previously the driver used a table to store all active open sockets.
This meant that the listener socket/port could access the accepting
install the file descriptor after accept.
Now the listener will create the port and install the descriptor and
pass the new
port to the erlang side and no locking is involved on the driver level.
On 14 dec 2007, at 16.18, Joel Reymont wrote:
> What is the advantage of locking a driver in memory with
> driver_lock_driver to make it behave like one of Erlang's statically
> linked drivers?
> Also, when should I use driver_create_port? I can't see a case where I
> would want to create a port from within a driver.
> Thanks, Joel
> erlang-questions mailing list
More information about the erlang-questions