<div dir="ltr"><div class="gmail_extra">This was an interesting scenario. Similar issue of _SC_NPROCESSORS_ONLN not reporting all available processors was also reported in some NVIDIA forum: <a href="https://devtalk.nvidia.com/default/topic/744695/number-of-cpu-cores-online-in-jetson-tk1/">https://devtalk.nvidia.com/default/topic/744695/number-of-cpu-cores-online-in-jetson-tk1/</a></div><div class="gmail_extra"><br></div><div class="gmail_extra">Has anyone else seen this problem? Is there a cleaner fix?</div><div class="gmail_extra">Pradeep.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">On Tue, Feb 9, 2016 at 3:57 PM, <span dir="ltr"><<a href="mailto:dnyaneshwar@multicorewareinc.com" target="_blank">dnyaneshwar@multicorewareinc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"># HG changeset patch<br>
# User Dnyaneshwar G <<a href="mailto:dnyaneshwar@multicorewareinc.com">dnyaneshwar@multicorewareinc.com</a>><br>
# Date 1455010589 -19800<br>
# Tue Feb 09 15:06:29 2016 +0530<br>
# Node ID 18b83aaee1b56e2048a425c25a452aa62c39da89<br>
# Parent 023e6051c4c63ab1633b2de0e8f37e6158796288<br>
threadpool: utilize all processors on embedded ARM platforms<br>
<br>
diff -r 023e6051c4c6 -r 18b83aaee1b5 source/common/threadpool.cpp<br>
--- a/source/common/threadpool.cpp Fri Feb 05 15:13:57 2016 +0530<br>
+++ b/source/common/threadpool.cpp Tue Feb 09 15:06:29 2016 +0530<br>
@@ -528,6 +528,10 @@<br>
SYSTEM_INFO sysinfo;<br>
GetSystemInfo(&sysinfo);<br>
return sysinfo.dwNumberOfProcessors;<br>
+#elif __unix__ && X265_ARCH_ARM<br>
+ /* Return the number of processors configured by OS. Because, most embedded linux distributions<br>
+ * uses only one processor as the scheduler doesn't have enough work to utilize all processors */<br>
+ return sysconf(_SC_NPROCESSORS_CONF);<br>
#elif __unix__<br>
return sysconf(_SC_NPROCESSORS_ONLN);<br>
#elif MACOS<br>
_______________________________________________<br>
x265-devel mailing list<br>
<a href="mailto:x265-devel@videolan.org">x265-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
</blockquote></div><br></div></div>