<?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: Linode&#8217;s Marketing Gimmick</title>
	<atom:link href="http://www.sirspanky.com/informative/linodes-marketing-gimmick/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sirspanky.com/informative/linodes-marketing-gimmick/</link>
	<description>Personal jorunal of a professional geek - James Pearce in Perth, Australia</description>
	<lastBuildDate>Mon, 09 Jan 2012 23:58:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jed Smith</title>
		<link>http://www.sirspanky.com/informative/linodes-marketing-gimmick/comment-page-1/#comment-5701</link>
		<dc:creator>Jed Smith</dc:creator>
		<pubDate>Sat, 07 Nov 2009 23:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sirspanky.com/?p=788#comment-5701</guid>
		<description>We use 1024 MB per GB, as everyone should. The disparity you&#039;re seeing is because you used a paravirtualized kernel -- something Slicehost does not support -- which differs in the way memory is reported to the VM.

On a Linode 360 I use for development which is running 2.6.18, the memory reported by &quot;free -k&quot; is 368,860k (exactly 360 MB reported by &quot;free -m&quot;). On a Linode 720 that I use for my personal site, running paravirtualized 2.6.31, &quot;free -k&quot; reports 721,132k (704 MB reported by &quot;free -m&quot;). We&#039;re not sure why this occurs, but my best guess is that the memory the kernel uses or reserves for itself is no longer contained in the total RAM available count.

We&#039;re still trying to narrow down why this occurs, but it is not a marketing gimmick. Feel free to e-mail me directly at jed at linode.com or open a ticket if you have any further questions; I guarantee you that we&#039;re not misleading you.</description>
		<content:encoded><![CDATA[<p>We use 1024 MB per GB, as everyone should. The disparity you&#8217;re seeing is because you used a paravirtualized kernel &#8212; something Slicehost does not support &#8212; which differs in the way memory is reported to the VM.</p>
<p>On a Linode 360 I use for development which is running 2.6.18, the memory reported by &#8220;free -k&#8221; is 368,860k (exactly 360 MB reported by &#8220;free -m&#8221;). On a Linode 720 that I use for my personal site, running paravirtualized 2.6.31, &#8220;free -k&#8221; reports 721,132k (704 MB reported by &#8220;free -m&#8221;). We&#8217;re not sure why this occurs, but my best guess is that the memory the kernel uses or reserves for itself is no longer contained in the total RAM available count.</p>
<p>We&#8217;re still trying to narrow down why this occurs, but it is not a marketing gimmick. Feel free to e-mail me directly at jed at linode.com or open a ticket if you have any further questions; I guarantee you that we&#8217;re not misleading you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

