2010/1/5 Stephen Wille Padnos <[email protected]>: >> That is normal if you use the ISOLCPUS option, the core dedicated to >> the RT threads doesn't show up in the resource monitor.
> Actually, that's not true. The core is still there, and is still > monitored by the normal tools. The only thing ISOLCPUS does is tell the > Linux scheduler not to put any tasks on that CPU by default. Tasks can > still set their processor affinity to that CPU if they like, and those > tasks will still show up in tools such as top. What I was doing was repeating section 7.2 from that link, which states that the system monitor will show the second CPU / Core at 0% load, even though it is busy with the realtime tasks. That certainly matches my experience with an SMP, RT kernel. I have 0% load in System Monitor on CPU1, and CPU0 shows less load than before, combined with a latency test that has dropped from 15,000 to about 6,000. -- atp ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
