<?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: Kent Smith of LSI SandForce Delivers Presentation on Over-Provisioning &#8211; FMS 2012 Update	</title>
	<atom:link href="https://www.thessdreview.com/daily-news/latest-buzz/kent-smith-of-lsi-sandforce-delivers-presentation-on-over-provisioning-at-fms-2012/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.thessdreview.com/daily-news/latest-buzz/kent-smith-of-lsi-sandforce-delivers-presentation-on-over-provisioning-at-fms-2012/</link>
	<description>The Worlds Dedicated SSD Education and Review Resource &#124;</description>
	<lastBuildDate>Fri, 30 Nov 2012 17:44:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Anonymous Coward		</title>
		<link>https://www.thessdreview.com/daily-news/latest-buzz/kent-smith-of-lsi-sandforce-delivers-presentation-on-over-provisioning-at-fms-2012/#comment-13972</link>

		<dc:creator><![CDATA[Anonymous Coward]]></dc:creator>
		<pubDate>Fri, 30 Nov 2012 17:44:00 +0000</pubDate>
		<guid isPermaLink="false">https://thessdreview.com/?p=55917#comment-13972</guid>

					<description><![CDATA[https://www.google.com/patents/US20120054415

SandForce presumably uses some sort of differential information 
update. When a block is modified, you find the difference between the 
old data and the new data. If the difference is small, you can just 
encode it over a smaller number of bits in the flash page. If you do the
 difference encoding, you cannot gc the old data unless you reassemble 
and rewrite the new data to a different location.

Difference encoding requires more time (extra read, processing, etc).
 So, you must not do it when the write buffer is close to full. You can 
always choose whether or not you do differential encoding.

It is definitely not deduplication. You can think of it as compression.]]></description>
			<content:encoded><![CDATA[<p><a href="https://www.google.com/patents/US20120054415" rel="nofollow ugc">https://www.google.com/patents/US20120054415</a></p>
<p>SandForce presumably uses some sort of differential information<br />
update. When a block is modified, you find the difference between the<br />
old data and the new data. If the difference is small, you can just<br />
encode it over a smaller number of bits in the flash page. If you do the<br />
 difference encoding, you cannot gc the old data unless you reassemble<br />
and rewrite the new data to a different location.</p>
<p>Difference encoding requires more time (extra read, processing, etc).<br />
 So, you must not do it when the write buffer is close to full. You can<br />
always choose whether or not you do differential encoding.</p>
<p>It is definitely not deduplication. You can think of it as compression.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
