IT Runs on Java 8

Re:IT Runs on Java 8 by MaxBarraclough on Saturday May 11, 2019 @12:15PM (#19886855)

> a fiber that tries to block inside a native call, i.e., when there is a native frame on the fiber's stack, will be "pinned" and block the underlying kernel thread.

Doesn't this boil down to the native function blocking the thread?

How about the C API/ABI of JNI? Will there be additions there for better supporting concurrency (i.e. not simply blocking)? Or can that be handled today, with something akin to callbacks?

[ Parent | on HN ]

Re:IT Runs on Java 8 by pron on Saturday May 11, 2019 @12:30PM (#19886955)

If the native routine blocks the kernel thread, it blocks, and if not, it doesn't. While something could hypothetically be done about blocking native routines, we don't see it as an important use case. Calling blocking native code from Java is quite uncommon. We've so far identified only one common case, DNS lookup, and will address it specifically.

[ Parent | on HN ]

Re:IT Runs on Java 8 by MaxBarraclough on Saturday May 11, 2019 @12:47PM (#19887067)

Nice. So going 100% async is a real possibility?

[ Parent | on HN ]

Re:IT Runs on Java 8 by pron on Tuesday May 14, 2019 @09:54AM (#19909436)

I'm not sure what that means.

[ Parent | on HN ]