[concurrency-interest] JNI signaling back to a thread/concurrentstructure?

Andrew Lentvorski bsder at allcaps.org
Tue Jul 14 20:38:50 EDT 2015


On 7/14/15, 2:21 AM, David Holmes wrote:

> Use JNI to invoke Thread.interrupt. That will unblock the sleep, or most
> other concurrency-based blocking mechanisms.

Is that going to be kosher?

Calling back from JNI to Java to to invoke Thread.interrupt seems like
I'm going to set off a cascade of actions will trigger priority inversion.

Any allocation of memory will pull a mutex that will cause a priority
inversion.

-a

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20150714/825c7a70/attachment.bin>


More information about the Concurrency-interest mailing list