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

<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
   xmlns="http://purl.org/rss/1.0/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/"
   xmlns:dcterms="http://purl.org/dc/terms/"

>
<channel rdf:about="http://www.citeulike.org/about">
<pubDate>Thu, 21 Aug 2008 15:14:29 BST</pubDate>


	<title>CiteULike: dfsweeney library [7 articles]</title>
	<description>CiteULike: dfsweeney library [7 articles]</description>


	<link>http://www.citeulike.org/user/dfsweeney</link>
	<dc:publisher>CiteULike.org</dc:publisher>
	<dc:language>en-gb</dc:language>
	<dc:rights>Copyright &#169; 2004-2008 citeulike.org</dc:rights>
	<items>
    <rdf:Seq>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/2960"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/1152"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/1138"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/1136"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/1135"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/1134"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/dfsweeney/article/1133"/>

	</rdf:Seq>
	</items>
	</channel>


<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/2960">
    <title>Foundations for the study of software architecture</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/2960</link>
    <description>&lt;i&gt;SIGSOFT Softw. Eng. Notes, Vol. 17, No. 4. (October 1992), pp. 40-52.&lt;/i&gt;</description>
    <dc:title>Foundations for the study of software architecture</dc:title>

    <dc:creator>Dewayne Perry</dc:creator>
    <dc:creator>Alexander Wolf</dc:creator>
    <dc:identifier>doi:10.1145/141874.141884</dc:identifier>
    <dc:source>SIGSOFT Softw. Eng. Notes, Vol. 17, No. 4. (October 1992), pp. 40-52.</dc:source>
    <dc:date>2004-12-07T16:24:37-00:00</dc:date>
    <prism:publicationYear>1992</prism:publicationYear>
    <prism:publicationName>SIGSOFT Softw. Eng. Notes</prism:publicationName>
    <prism:issn>0163-5948</prism:issn>
    <prism:volume>17</prism:volume>
    <prism:number>4</prism:number>
    <prism:startingPage>40</prism:startingPage>
    <prism:endingPage>52</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>software_architecture</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/1152">
    <title>Eigen values and expanders</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/1152</link>
    <description>&lt;i&gt;Combinatorica, Vol. 6, No. 2. (1986), pp. 83-96.&lt;/i&gt;</description>
    <dc:title>Eigen values and expanders</dc:title>

    <dc:creator>N Alon</dc:creator>
    <dc:source>Combinatorica, Vol. 6, No. 2. (1986), pp. 83-96.</dc:source>
    <dc:date>2004-11-29T20:52:19-00:00</dc:date>
    <prism:publicationYear>1986</prism:publicationYear>
    <prism:publicationName>Combinatorica</prism:publicationName>
    <prism:issn>0209-9683</prism:issn>
    <prism:volume>6</prism:volume>
    <prism:number>2</prism:number>
    <prism:startingPage>83</prism:startingPage>
    <prism:endingPage>96</prism:endingPage>
    <prism:publisher>Springer-Verlag New York, Inc.</prism:publisher>
    <prism:category>linear_algebra</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/1138">
    <title>Reconsidering custom memory allocation</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/1138</link>
    <description>&lt;i&gt;Vol. 37, No. 11. (November 2002), pp. 1-12.&lt;/i&gt;</description>
    <dc:title>Reconsidering custom memory allocation</dc:title>

    <dc:creator>Emery Berger</dc:creator>
    <dc:creator>Benjamin Zorn</dc:creator>
    <dc:creator>Kathryn Mckinley</dc:creator>
    <dc:identifier>doi:10.1145/582419.582421</dc:identifier>
    <dc:source>Vol. 37, No. 11. (November 2002), pp. 1-12.</dc:source>
    <dc:date>2004-11-29T17:31:47-00:00</dc:date>
    <prism:publicationYear>2002</prism:publicationYear>
    <prism:volume>37</prism:volume>
    <prism:number>11</prism:number>
    <prism:startingPage>1</prism:startingPage>
    <prism:endingPage>12</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>memory</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/1136">
    <title>Language Support for Regions</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/1136</link>
    <description>&lt;i&gt;(2001), pp. 70-80.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Region-based memory management systems structure memory by grouping objects in regions under program control. Memory is reclaimed by deleting regions, freeing all objects stored therein. Our compiler for C with regions, RC, prevents unsafe region deletions by keeping a count of references to each region. Using type annotations that make the structure of a program's regions more explicit, we reduce the overhead of reference counting from a maximum of 27% to a maximum of 11% on a suite of...</description>
    <dc:title>Language Support for Regions</dc:title>

    <dc:creator>David Gay</dc:creator>
    <dc:creator>Alexander Aiken</dc:creator>
    <dc:source>(2001), pp. 70-80.</dc:source>
    <dc:date>2004-11-29T17:20:16-00:00</dc:date>
    <prism:publicationYear>2001</prism:publicationYear>
    <prism:startingPage>70</prism:startingPage>
    <prism:endingPage>80</prism:endingPage>
    <prism:category>memory</prism:category>
    <prism:category>regions</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/1135">
    <title>Memory Management with Explicit Regions</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/1135</link>
    <description>&lt;i&gt;(1998), pp. 313-323.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Much research has been devoted to studies of and algorithms for memory management based on garbage collection or explicit allocation and deallocation. An alternative approach, region-based memory management, has been known for decades, but has not been wellstudied. In a region-based system each allocation specifies a region, and memory is reclaimed by destroying a region, freeing all the storage allocated therein. We show that on a suite of allocation-intensive C programs, regions are...</description>
    <dc:title>Memory Management with Explicit Regions</dc:title>

    <dc:creator>David Gay</dc:creator>
    <dc:creator>Alexander Aiken</dc:creator>
    <dc:source>(1998), pp. 313-323.</dc:source>
    <dc:date>2004-11-29T17:17:38-00:00</dc:date>
    <prism:publicationYear>1998</prism:publicationYear>
    <prism:startingPage>313</prism:startingPage>
    <prism:endingPage>323</prism:endingPage>
    <prism:category>memory</prism:category>
    <prism:category>regions</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/1134">
    <title>Region-Based Memory Management</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/1134</link>
    <description>&lt;i&gt;Information and Computation (1997)&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;This paper describes a memory management discipline for programs that perform dynamic memory allocation and de-allocation. At runtime, all values are put into regions. The store consists of a stack of regions. All points of region allocation and deallocation are inferred automatically, using a type and effect based program analysis. The scheme does not assume the presence of a garbage collector. The scheme was first presented by Tofte and Talpin (1994); subsequently, it has been tested in The...</description>
    <dc:title>Region-Based Memory Management</dc:title>

    <dc:creator>Mads Tofte</dc:creator>
    <dc:creator>Jean-Pierre Talpin</dc:creator>
    <dc:source>Information and Computation (1997)</dc:source>
    <dc:date>2004-11-29T17:17:03-00:00</dc:date>
    <prism:publicationYear>1997</prism:publicationYear>
    <prism:publicationName>Information and Computation</prism:publicationName>
    <prism:category>memory</prism:category>
    <prism:category>regions</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/dfsweeney/article/1133">
    <title>A hardware implementation of realloc function</title>
    <link>http://www.citeulike.org/user/dfsweeney/article/1133</link>
    <description>&lt;i&gt;Integration, the VLSI Journal, Vol. 28, No. 2. (January 1999), pp. 173-184.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The memory intensive nature of object-oriented languages such as C++ and Java has created the need of a high-performance dynamic memory management. Object-oriented applications often generate higher memory intensity in the heap region. Thus, high-performance memory manager is needed to cope with such applications. As today's VLSI technology advances, it becomes more and more attractive to map basic software algorithms such as malloc(&#160;), free(&#160;), and realloc(&#160;) into hardware. This paper presents a hardware design of realloc function that fully utilizes the advantage of combinational logic. There are two steps needed to complete a reallocation process: (a) try to reallocate on the original memory block and (b) if (a) failed, allocate another memory block and copy the contents of the original block to this new location. In our scheme, (a) can be done in constant time. For (b), the allocation of new memory block and the deallocation of original block are done in constant time. The hardware complexity of proposed scheme (i.e. X-unit, RS-unit, and ESG-unit) is O(n), where n represents the size of bit-map.</description>
    <dc:title>A hardware implementation of realloc function</dc:title>

    <dc:creator>Witawas Srisa-An</dc:creator>
    <dc:creator>C Dan</dc:creator>
    <dc:creator>J Morris</dc:creator>
    <dc:identifier>doi:10.1016/S0167-9260(99)00016-4</dc:identifier>
    <dc:source>Integration, the VLSI Journal, Vol. 28, No. 2. (January 1999), pp. 173-184.</dc:source>
    <dc:date>2004-11-29T17:07:56-00:00</dc:date>
    <prism:publicationYear>1999</prism:publicationYear>
    <prism:publicationName>Integration, the VLSI Journal</prism:publicationName>
    <prism:volume>28</prism:volume>
    <prism:number>2</prism:number>
    <prism:startingPage>173</prism:startingPage>
    <prism:endingPage>184</prism:endingPage>
    <prism:category>memory</prism:category>
</item>



</rdf:RDF>

