[External] : Re: Native interop with Virtual Threads

[Alan Bateman]

On 27/06/2023 00:11, Robert Engels wrote:
> Go also locks the carrier thread in this arbitrary native case - and simply spawns a new one if needed.
>
With virtual threads then this kind of thing would be possible if some 
of the interface to the scheduler were exposed. In particular the 
exploration into custom schedulers might have to expose some way to 
temporarily compensate for pinned threads. As Ron said, we haven't seen 
too many cases where there are upcalls from native code and where the 
Java code blocks. The other scenario of a downcall that blocks in a 
syscall is a lot more likely.

-Alan