<div class="gmail_quote">2012/1/29 carlos_wang <span dir="ltr"><<a href="mailto:1988wzc@gmail.com">1988wzc@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<p>Hi all: <br> I got a problem in understanding why resync-cache uses LRU as its mechanism. I think that a queue is enough to realize the LRU functions. Why does it use LRU anyway? </p>
<p> Thanks in advance. </p><span class="HOEnZb"><font color="#888888">
<p> Carlos.</p></font></span></blockquote></div>
<div><font color="#888888">Blocks may be "resynced" by new application writes as well.</font></div>
<div><font color="#888888"></font> </div>
<div>Thanks, but according to the code, Once application writes on a DRBD device, act_log will cache the active sector in al_extent, writes the last extent in lru list on the disk, And never known by resync extent, of course in right connection. How blocks know "resynced" by new application writes? When drbd begin resyncing, the sector will start from the first sector to last sector, so I think it's no need to use LRU as its resync mechanism.</div>