Eric H. Johnson wrote: >Mario, > >I only see one ACPI setting in the BIOS. It is listed as 'ACPI Suspend >State' and currently set to 'S3 State'. The only other option is 'S1 State'. >I also see in the BIOS a setting for 'Hyper Threading Technology'. It is set >to 'Enable'. > > Excellent that you have it working!
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. - Steve ------------------------------------------------------------------------------ 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
