The latest jetpack 4.64 still couldn’t fix this problem. That means the design of TX2 has some defect.
Since the performance of first Denver cores in TK1 is similar to A15 quad-core, the performance of Denver cores in TX2 should be equal to A57 quad-core. Thus, the TX2 is deprived of its half power if the Denver cores are disabled.
My understanding is that Denver cores are better off from Linux scheduling, but you can use these for your own purpose using taskset or sched_setaffinity. Searching this forum you would find some examples.
I’ll add that if you look at “cat /proc/cmdline”, then you’ll see “isolcpus=1-2”. You can make these “general” cores by removing that isolation. At the end of the “APPEND” key/value pair of “/boot/extlinux/extlinux.conf”, just add this (which supersedes the earlier value):
isolcpus=
The power consumption of the Denver cores is better than that of the regular cores, but the latency also goes up. One would normally schedule tasks which don’t have a latency problem on the Denver cores.
It works this time(It doesn’t work last time). Thank you.
With the Denver cores enabled, its performance is much fluent.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.