<?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 NPTL in Linux kernel2.6 on Hyperthreading Processor in Intel® Moderncode for Parallel Architectures</title>
    <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/NPTL-in-Linux-kernel2-6-on-Hyperthreading-Processor/m-p/984640#M5816</link>
    <description>The introduction of NPTL into Redhat 9.0 kernel 2.6 has solve the Java threading problems on scalability and signal handling. &lt;BR /&gt;&lt;BR /&gt;Correct me if I am wrong on this perception:&lt;BR /&gt;For example, an application consist of 5 Java threads, map to 5 kernel threads created from the NPTL (clone system call) using 1 to 1 mapping model respectively. &lt;BR /&gt;&lt;BR /&gt;If my perception is correct:&lt;BR /&gt;&lt;BR /&gt;1)How can these 5 kernel threads being scheduled into the HT dual processors which consist of 4 logical processors?&lt;BR /&gt;&lt;BR /&gt;2) How the kernel threads scheduler knows the number of logical processors exist?&lt;BR /&gt;&lt;BR /&gt;3)  How is the naming of the logical processors in a DP with HT enabled?Is it:&lt;BR /&gt;&lt;BR /&gt;Physical processor 0:  Logical processor 0&lt;BR /&gt;Physical processor 0:  Logical processor 1&lt;BR /&gt;Physical processor 1:  Logical processor 2&lt;BR /&gt;Physical processor 1:  Logical processor 3&lt;BR /&gt;&lt;BR /&gt;OR:&lt;BR /&gt;&lt;BR /&gt;Physical processor 0:  Logical processor 0&lt;BR /&gt;Physical processor 1:  Logical processor 1&lt;BR /&gt;Physical processor 0:  Logical processor 2&lt;BR /&gt;Physical processor 1:  Logical processor 3&lt;BR /&gt; Correct me if I am wrong. Does this dependent on the kernel version installed?&lt;BR /&gt;&lt;BR /&gt;Thank you: meileng&lt;BR /&gt;</description>
    <pubDate>Wed, 24 Sep 2003 16:12:35 GMT</pubDate>
    <dc:creator>yaumeileng</dc:creator>
    <dc:date>2003-09-24T16:12:35Z</dc:date>
    <item>
      <title>NPTL in Linux kernel2.6 on Hyperthreading Processor</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/NPTL-in-Linux-kernel2-6-on-Hyperthreading-Processor/m-p/984640#M5816</link>
      <description>The introduction of NPTL into Redhat 9.0 kernel 2.6 has solve the Java threading problems on scalability and signal handling. &lt;BR /&gt;&lt;BR /&gt;Correct me if I am wrong on this perception:&lt;BR /&gt;For example, an application consist of 5 Java threads, map to 5 kernel threads created from the NPTL (clone system call) using 1 to 1 mapping model respectively. &lt;BR /&gt;&lt;BR /&gt;If my perception is correct:&lt;BR /&gt;&lt;BR /&gt;1)How can these 5 kernel threads being scheduled into the HT dual processors which consist of 4 logical processors?&lt;BR /&gt;&lt;BR /&gt;2) How the kernel threads scheduler knows the number of logical processors exist?&lt;BR /&gt;&lt;BR /&gt;3)  How is the naming of the logical processors in a DP with HT enabled?Is it:&lt;BR /&gt;&lt;BR /&gt;Physical processor 0:  Logical processor 0&lt;BR /&gt;Physical processor 0:  Logical processor 1&lt;BR /&gt;Physical processor 1:  Logical processor 2&lt;BR /&gt;Physical processor 1:  Logical processor 3&lt;BR /&gt;&lt;BR /&gt;OR:&lt;BR /&gt;&lt;BR /&gt;Physical processor 0:  Logical processor 0&lt;BR /&gt;Physical processor 1:  Logical processor 1&lt;BR /&gt;Physical processor 0:  Logical processor 2&lt;BR /&gt;Physical processor 1:  Logical processor 3&lt;BR /&gt; Correct me if I am wrong. Does this dependent on the kernel version installed?&lt;BR /&gt;&lt;BR /&gt;Thank you: meileng&lt;BR /&gt;</description>
      <pubDate>Wed, 24 Sep 2003 16:12:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/NPTL-in-Linux-kernel2-6-on-Hyperthreading-Processor/m-p/984640#M5816</guid>
      <dc:creator>yaumeileng</dc:creator>
      <dc:date>2003-09-24T16:12:35Z</dc:date>
    </item>
  </channel>
</rss>

