Steve (and others), I was finally able to get it to configure similar to Eric's setup (althought I am running 2.6.27-magma due to problems with the 2.6.24 kernel not playing nicely with my CPU fan -- a known problem), but have an odd thing which seems to require a CPU hog process in another terminal. If the process is not there, then the RT thread seems to stall waiting for the scheduler to give it a time slice. Once I run the hog, in another terminal it straightens right out. Any suggestions?
Also from the online documentation I find conflicting information regarding the following settings: Tickless System (Dynamic Ticks) High Resolution Timer Support Preemption Model (***) Compat VDSO support Power Management support Any pointers on how to sort out the thread inconsistencies would be appreciated. Best regards, EBo -- Stephen Wille Padnos <spad...@sover.net> said: > Two things come to mind. First, disable hyperthreading. It's rare for > HT to help at all these days, and for many workloads it's a net loss. > Second, try restricting Linux from using one core. You do this by > adding a kernel boot parameter to GRUB: "isolcpus=1" (or "isolcpus=2,3" > if you leave HT on) This will prevent Linux from scheduling processes > on the second core. If you have compiled RTAPI against SMP kernel > headers, then RTAPI will automatically use the highest numbered CPU for > realtime tasks. > > If you do this, and don't see much improvement, then here's one more > thing to try. You'll need two terminals open for this. In one > terminal, enter the following line: > while true ; do echo "nothing" > /dev/null ; done > This will run forever (until you press ctrl-C), and will chew up CPU > cycles on the non-RT core. Leave that running, and run latency-test in > the other terminal. > > On the dual-core systems I set up (with Chris' old SMP test kernel), > using a CPU hog on the non-RT core improved things dramatically. ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
