has a separate native thread and in LispWorks 6.0 these threads can run simultaneously.
Note: In LispWorks 5.1 and earlier versions, you can have many runnable
objects/native threads, but Lisp code can only run in one thread at a time and a lock is used to enforce this. This can limit performance on a computer with multiple CPU cores. When a foreign function is called using the FLI, the lock is released until the function returns. This allows other Lisp threads to run, for instance while waiting for a database query to execute.
You can call back into Lisp using
in any thread, without any other setup.
Note: In a LispWorks 5.0 executable on Microsoft Windows you must first call
before calling back into Lisp, but in LispWorks 5.1 and later versions this setup is handled automatically (and
does not exist).
Threads running Lisp code can be rescheduled preemptively, so if you call into Lisp from more than one thread simultaneously and one request takes a long time then it will not delay the requests in other threads.