Recent content by Pete Vieira

I wondered if this was possibly happening, I just don't know enough about the details. If this is happening, what options are there besides switching graphics drivers or waiting for an update that fixes this intentional "issue"?

That'd be pretty convenient. The hotfix is Windows only currently. I guess I'll just have to wait to try it out. Thanks

The realtime process runs at about 20% CPU for it's isolated core. But I replaced everything in the control loop with a usleep between 100 and 500 us, so that there's just a usleep and then the higher level clock_nanosleep(), and the overruns are still persistent. Just opening a web browser or...

I tried isolating several different CPUs but none of them made any difference.

Not at this point. The latest available from the Software & Updates menu's Additional Drivers tab is 352.21, which is the latest for my graphics card on the NVIDIA website. I tried this, and if anything it made timing worse for the realtime process.

Looking at /proc/interrupts I notice that with the nvidia driver running, there's an nvidia irq, but with the nouveau driver I don't see any irq for it.

Thanks for the response. I have tried core 15. Didn't notice any difference. I also tried writing a different cpu affinity to the nvidia irq smp_affinity file, but that didn't seem to change anything and it wasn't permanent.

Hi, I'm new, but failed to find this topic on this site, so if this question is answered, please point me in the right direction. I'm trying to understand how a 3D visualization program and graphics driver affects a realtime process that runs on an isolated cpu. See my setup, test results and...