<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Cost of Software-Based Memory Management Without Virtual Memory · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2009.06789/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2009.06789/feed.xml" rel="self" type="application/rss+xml" /><item><title>The Cost of Software-Based Memory Management Without Virtual Memory — mentioned by awelkie</title><link>https://news.ycombinator.com/item?id=27048776</link><guid isPermaLink="false">urn:hackerpapers:mention:2009.06789:27048776</guid><pubDate>Wed, 05 May 2021 11:55:12 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;ve been wondering recently to what extent formal verification could be used to simplify CPU hardware and ISAs. For example, MMUs are unnecessary if the OS verifies that all programs only access memory that&amp;#x27;s been allocated to it. This paper[0] seems to imply that the savings would be non-negligible. Also interrupts and context switching could be avoided if programs are cooperatively scheduled and verified that they always yield after an appropriate amount of time. Those two examples are the only ones I could come up with, but I suspect that&amp;#x27;s because I don&amp;#x27;t know very much about hardware…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2009.06789/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.AR</category></item><item><title>The Cost of Software-Based Memory Management Without Virtual Memory — mentioned by eternalban</title><link>https://news.ycombinator.com/item?id=24511556</link><guid isPermaLink="false">urn:hackerpapers:mention:2009.06789:24511556</guid><pubDate>Fri, 18 Sep 2020 00:18:34 GMT</pubDate><description>&lt;p&gt;It&amp;#x27;s actually pretty cool of arxiv to provide a gzip of the source files for the pdf, here TeX: https://arxiv.org/format/2009.06789&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2009.06789/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.AR</category></item><item><title>The Cost of Software-Based Memory Management Without Virtual Memory — HN submission</title><link>https://news.ycombinator.com/item?id=24503773</link><guid isPermaLink="false">urn:hackerpapers:submission:2009.06789:24503773</guid><pubDate>Thu, 17 Sep 2020 12:28:51 GMT</pubDate><description>&lt;p&gt;The Cost of Software-Based Memory Management Without Virtual Memory&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;72 points; 21 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2009.06789/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.AR</category></item><item><title>The Cost of Software-Based Memory Management Without Virtual Memory — HN submission</title><link>https://news.ycombinator.com/item?id=24499158</link><guid isPermaLink="false">urn:hackerpapers:submission:2009.06789:24499158</guid><pubDate>Wed, 16 Sep 2020 23:13:00 GMT</pubDate><description>&lt;p&gt;The Cost of Software-Based Memory Management Without Virtual Memory&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;4 points; 1 discussion reply on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2009.06789/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.AR</category></item></channel></rss>
