3 messages in net.java.dev.jna.usersRE: [jna-users] threads and JNA
FromSent OnAttachments
Glick, Gene (GE Indust, Security)Oct 29, 2007 11:29 am 
Timothy WallOct 29, 2007 12:45 pm 
Glick, Gene (GE Indust, Security)Oct 29, 2007 1:39 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [jna-users] threads and JNAActions...
From:Glick, Gene (GE Indust, Security) (gene@ge.com)
Date:Oct 29, 2007 1:39:54 pm
List:net.java.dev.jna.users

JNA calls shouldn't affect thread scheduling any more than any other JNI call. It *will* lock memory on primitive array arguments in some circumstances, but I don't think that's your issue.

Probably right - but I'm getting closer :)

Note that if your native function hogs the CPU, your other threads may not get much time to run, but that's not JNA's fault.

OK. I have to dig some more to find who's locking out who. Thanks for the tips :D

gene