<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/20741/">
    <title>LWN: Comments on "The new NUMA scheduler"</title>
    <link>http://lwn.net/Articles/20741/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;The new NUMA scheduler&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/21369/rss" />
	<rdf:li resource="http://lwn.net/Articles/20958/rss" />
	<rdf:li resource="http://lwn.net/Articles/20849/rss" />
	<rdf:li resource="http://lwn.net/Articles/20846/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/21369/rss">
      <title>The new NUMA scheduler</title>
      <link>http://lwn.net/Articles/21369/rss</link>
      <dc:date>2003-01-29T17:12:39+00:00</dc:date>
      <dc:creator>hbaum</dc:creator>
      <description>
      The NUMA scheduler patches that have been around since October consisted of two pieces - balance-on-exec, and NUMA-aware-load-balance.  The three line patch that Martin wrote replaced the NUMA-aware-load-balance, but still relied on the balance-on-exec patch being in place.  So it is not accurate to state that the NUMA scheduler patch which provided equivalent performance to the original NUMA scheduler patch was simply a three line patch.  Rather one half of the original NUMA scheduler patch was replaced by a three line patch.  The balance-on-exec portion of the NUMA scheduler patch was still required to get equivalent performance.&lt;p&gt;Regarding something like this going in after feature freeze - with Martin's contribution, the NUMA scheduler changes have no impact on non-NUMA systems.  The balance-on-exec portion of the patch was always a NUMA only piece of code, and Martin's contribution removed the need for an invasive change to the load balancer. 
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/20958/rss">
      <title>three-line patch?</title>
      <link>http://lwn.net/Articles/20958/rss</link>
      <dc:date>2003-01-23T21:27:52+00:00</dc:date>
      <dc:creator>mbligh</dc:creator>
      <description>
      I wrote the &amp;quot;3-line&amp;quot; patch to show how non-invasive a NUMA scheduler could be. It also changes the design of the NUMA scheduler to become a set of &amp;quot;concentric circles&amp;quot; as far as load-balance is concerned - I think this is a better design.&lt;p&gt;IMO, in the post-freeze environment, the only way to proceed is small, well contained patches that obviously don't break anyone else ...&lt;p&gt;M.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/20849/rss">
      <title>three-line patch?</title>
      <link>http://lwn.net/Articles/20849/rss</link>
      <dc:date>2003-01-23T03:02:05+00:00</dc:date>
      <dc:creator>corbet</dc:creator>
      <description>
      Sorry, I should have been more explicit there.  The patch was by Martin Bligh, who has been working with the NUMA scheduler for a while.  &lt;a href=&quot;http://lwn.net/Articles/20848/&quot;&gt;Here's a copy&lt;/a&gt; with his explanation of what's going on.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/20846/rss">
      <title>three-line patch?</title>
      <link>http://lwn.net/Articles/20846/rss</link>
      <dc:date>2003-01-23T02:54:20+00:00</dc:date>
      <dc:creator>cpeterso</dc:creator>
      <description>
      I am a little confused about the origin of the &quot;three-line patch&quot;. Was that patch taken &lt;i&gt;from&lt;/i&gt; the ongoing NUMA schduler work? Or was it written by an &quot;outsider&quot; who demonstrated the same benefits as the &quot;big&quot; NUMA scheduler, but with far fewer lines of code?

      
      </description>
    </item>
</rdf:RDF>

