<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Xen and Swap</title>
	<atom:link href="http://etbe.coker.com.au/2008/05/22/xen-and-swap/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2008/05/22/xen-and-swap/</link>
	<description>Linux, politics, and other interesting things</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:45:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2008/05/22/xen-and-swap/comment-page-1/#comment-14129</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Fri, 23 May 2008 10:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=587#comment-14129</guid>
		<description>Devin: Interesting program, however it appears to have no support for rate limiting of memory access.  I want to be able to allocate X amount of memory and then access Y amount per second with Z amount of that access being writes.

Alex: When I had the idea I thought it would be a silver bullet, but the evidence suggests that isn&#039;t the case.  I look forward to someone telling me about another way to do it or pointing out a flaw in my testing.</description>
		<content:encoded><![CDATA[<p>Devin: Interesting program, however it appears to have no support for rate limiting of memory access.  I want to be able to allocate X amount of memory and then access Y amount per second with Z amount of that access being writes.</p>
<p>Alex: When I had the idea I thought it would be a silver bullet, but the evidence suggests that isn&#8217;t the case.  I look forward to someone telling me about another way to do it or pointing out a flaw in my testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Malinovich</title>
		<link>http://etbe.coker.com.au/2008/05/22/xen-and-swap/comment-page-1/#comment-14120</link>
		<dc:creator>Alex Malinovich</dc:creator>
		<pubDate>Thu, 22 May 2008 16:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=587#comment-14120</guid>
		<description>When I read the first paragraph here, it sounded like the silver bullet I&#039;ve been looking for: a way to allow a DomU to use more RAM than it should for brief periods. The big balancing act of administering Dom0&#039;s (at least in my experience), comes from having a large number (20+) of DomU&#039;s on a single Dom0. Here the goal is to have each domu have as little RAM allocated to it as possible, but to allow a way for it to temporarily grow without a reboot. Or, more specifically, to have just enough RAM to handle day-to-day operations, but to allow for more during special operations.

I&#039;d suspect that the numbers you&#039;re seeing have something to do with the way the swapping functionality in the kernel is implemented, though I really am not quite familiar enough with the kernel internals to make that judgement.

If you do throw together any Xen testing tools, I&#039;ll definitely make use of them. I&#039;m (un-)fortunate enough to get paid to work with Xen all day, and if I can get so much as a 1% improvement that can be quite important.</description>
		<content:encoded><![CDATA[<p>When I read the first paragraph here, it sounded like the silver bullet I&#8217;ve been looking for: a way to allow a DomU to use more RAM than it should for brief periods. The big balancing act of administering Dom0&#8242;s (at least in my experience), comes from having a large number (20+) of DomU&#8217;s on a single Dom0. Here the goal is to have each domu have as little RAM allocated to it as possible, but to allow a way for it to temporarily grow without a reboot. Or, more specifically, to have just enough RAM to handle day-to-day operations, but to allow for more during special operations.</p>
<p>I&#8217;d suspect that the numbers you&#8217;re seeing have something to do with the way the swapping functionality in the kernel is implemented, though I really am not quite familiar enough with the kernel internals to make that judgement.</p>
<p>If you do throw together any Xen testing tools, I&#8217;ll definitely make use of them. I&#8217;m (un-)fortunate enough to get paid to work with Xen all day, and if I can get so much as a 1% improvement that can be quite important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin Carraway</title>
		<link>http://etbe.coker.com.au/2008/05/22/xen-and-swap/comment-page-1/#comment-14105</link>
		<dc:creator>Devin Carraway</dc:creator>
		<pubDate>Thu, 22 May 2008 01:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=587#comment-14105</guid>
		<description>&gt; I am idly considering writing a program to exercise virtual memory for the purpose of benchmarking swap on virtual machines.

I wrote such a thing (http://devin.com/lookbusy/) a ways back, as part of a somewhat silly app to make fake system load of various sorts.  Might be useful to you, might not.</description>
		<content:encoded><![CDATA[<p>&gt; I am idly considering writing a program to exercise virtual memory for the purpose of benchmarking swap on virtual machines.</p>
<p>I wrote such a thing (<a href="http://devin.com/lookbusy/" rel="nofollow">http://devin.com/lookbusy/</a>) a ways back, as part of a somewhat silly app to make fake system load of various sorts.  Might be useful to you, might not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

