<?xml version="1.0"?>

<rss version="2.0">
  <channel>
    <title>Andrew Cowie</title>
    <link>http://research.operationaldynamics.com/blogs/andrew/software/research/</link>
    <description>Blog postings by Andrew Cowie about Open Source and Software Development</description>
    <language>en</language>
    <copyright>Copyright (c) 2008 Operational Dynamics Consulting Pty Ltd. All rights reserved. Not for redistribution or attribution without permission in writing.</copyright>

    <image>
      <url>http://research.operationaldynamics.com/images/andrew_Hackergotchi.png</url>
      <title>Operational Dynamics Research</title>
      <link>http://research.operationaldynamics.com/blogs/andrew/software/research/</link>
      <width>80</width>
      <height>86</height>
    </image>

    <lastBuildDate>Tue, 18 Nov 2008 01:36:00 GMT</lastBuildDate>

    <item>
      <title>Get Some</title>
      <link>http://research.operationaldynamics.com/blogs/andrew/software/research/drepper-on-memory.html</link>
      <description><![CDATA[<p>The other day I was wading through Ulrich Drepper&#8217;s <a href="http://people.redhat.com/drepper/cpumemory.pdf">paper</a> about how memory works these days and what programmers should do as a result.</p>

<p>My wife asked me what I was reading. I showed her the title and when she saw it concerned computer memory, she looked at me with a totally straight face and summed up the 114 page paper by answering &#8220;Yes, you should get some&#8221;.</p>

<p><em>Like most of Ulrich&#8217;s writing, this paper is immense: long on detail and well presented. I must admit that I agreed with many others that after having read the work I was left wondering what action, in practical terms, I should be taking as a result. Clearly most of this knowledge is very important for Kernel hackers and for those doing low level systems programming, but since I do higher level work (ie advising people with large enterprise systems), it is hard to asses the choices I might be making in the terms of what Ulrich describes. I can only hope that the people who work on the parts of the low level libraries that run next to the metal (such as drivers, GLib, and especially the VMs like the Java and Python runtimes) are aware of these issues and making design choices based on these insights.</em></p>

<p>AfC</p>
]]></description>
      <author>andrew@operationaldynamics.com (Andrew Cowie)</author>
      <category>/andrew/software/research</category>
      <pubDate>Mon, 25 Feb 2008 23:39:00 GMT</pubDate>
      <guid isPermaLink="false">drepper-on-memory</guid>
    </item>


  </channel>
</rss>
