<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic [solved] PARDISO doesn't recognize HTT threads in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829800#M5458</link>
    <description>Hi,&lt;DIV&gt;I want to do some benchmarking on pardiso. I have the problem that pardiso doesn't recognize HTT Threads.&lt;/DIV&gt;&lt;DIV&gt;I now that there won't be a performance gain, but I need this comparison for my bachelor thesis.&lt;/DIV&gt;&lt;DIV&gt;Our System has 8 Cores and 16 Threads.&lt;/DIV&gt;&lt;DIV&gt;Neither specifying iparm[2]=16 nor setting OMP_NUM_THREADS=16 does the job.&lt;/DIV&gt;&lt;DIV&gt;HTT is enabled in BIOS as the following output shows:&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 10 maps to package 0 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 6 maps to package 0 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 14 maps to package 0 core 1 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 7 maps to package 1 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 15 maps to package 1 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 3 maps to package 1 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 11 maps to package 1 core 1 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 1 maps to package 2 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 8 maps to package 2 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 4 maps to package 2 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 12 maps to package 2 core 1 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 5 maps to package 3 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 13 maps to package 3 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 2 maps to package 3 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 9 maps to package 3 core 1 thread 1&lt;/DIV&gt;OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 core 0 thread 0&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;The same problem applies to ISS and DSS.&lt;/DIV&gt;&lt;DIV&gt;Does anybody know what's the problem?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Soeren&lt;/DIV&gt;</description>
    <pubDate>Sat, 04 Sep 2010 15:16:05 GMT</pubDate>
    <dc:creator>Sören_Plönnigs</dc:creator>
    <dc:date>2010-09-04T15:16:05Z</dc:date>
    <item>
      <title>[solved] PARDISO doesn't recognize HTT threads</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829800#M5458</link>
      <description>Hi,&lt;DIV&gt;I want to do some benchmarking on pardiso. I have the problem that pardiso doesn't recognize HTT Threads.&lt;/DIV&gt;&lt;DIV&gt;I now that there won't be a performance gain, but I need this comparison for my bachelor thesis.&lt;/DIV&gt;&lt;DIV&gt;Our System has 8 Cores and 16 Threads.&lt;/DIV&gt;&lt;DIV&gt;Neither specifying iparm[2]=16 nor setting OMP_NUM_THREADS=16 does the job.&lt;/DIV&gt;&lt;DIV&gt;HTT is enabled in BIOS as the following output shows:&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 10 maps to package 0 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 6 maps to package 0 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 14 maps to package 0 core 1 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 7 maps to package 1 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 15 maps to package 1 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 3 maps to package 1 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 11 maps to package 1 core 1 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 1 maps to package 2 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 8 maps to package 2 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 4 maps to package 2 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 12 maps to package 2 core 1 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 5 maps to package 3 core 0 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 13 maps to package 3 core 0 thread 1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 2 maps to package 3 core 1 thread 0&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Info #171: KMP_AFFINITY: OS proc 9 maps to package 3 core 1 thread 1&lt;/DIV&gt;OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 core 0 thread 0&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;The same problem applies to ISS and DSS.&lt;/DIV&gt;&lt;DIV&gt;Does anybody know what's the problem?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Soeren&lt;/DIV&gt;</description>
      <pubDate>Sat, 04 Sep 2010 15:16:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829800#M5458</guid>
      <dc:creator>Sören_Plönnigs</dc:creator>
      <dc:date>2010-09-04T15:16:05Z</dc:date>
    </item>
    <item>
      <title>PARDISO doesn't recognize HTT threads</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829801#M5459</link>
      <description>Hi Soeren,&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;MKL dynamically changes the number of threads to the most optimal value. To disable this, please usemkl_set_dynamic(0) call.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;With best regards,&lt;/DIV&gt;&lt;DIV&gt;Konstantin&lt;/DIV&gt;</description>
      <pubDate>Mon, 06 Sep 2010 04:34:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829801#M5459</guid>
      <dc:creator>Konstantin_A_Intel</dc:creator>
      <dc:date>2010-09-06T04:34:16Z</dc:date>
    </item>
    <item>
      <title>PARDISO doesn't recognize HTT threads</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829802#M5460</link>
      <description>Soeren,&lt;DIV&gt;just two my cents -&lt;SPAN style="font-size: 10.8333px;"&gt;yes, the&lt;SPAN style="font-size: 9.02775px;"&gt;same problem applies to ISS and DSS and to all others MKL domains. Using MKL_DYNAMIC Environment variable and/or mkl_set_dynamic() service function will enable MKL to dynamically change the number of threads. By the default,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-size: 10.8333px;"&gt;&lt;SPAN style="font-size: 9.02775px;"&gt;&lt;DIV id="_mcePaste"&gt;MKL_DYNAMIC is TRUE and when&lt;SPAN style="font-size: 9.02778px;"&gt;MKL tries to use what it considers the best number ofthreads, up to the maximum number you specify.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;SPAN style="font-size: 9.02778px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;SPAN style="font-size: 9.02778px;"&gt;see more details into User's Guide.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;SPAN style="font-size: 9.02778px;"&gt;--Gennady&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-size: small;"&gt;&lt;SPAN style="font-size: 13px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 06 Sep 2010 05:09:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/solved-PARDISO-doesn-t-recognize-HTT-threads/m-p/829802#M5460</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2010-09-06T05:09:12Z</dc:date>
    </item>
  </channel>
</rss>

