[Drbd-dev] Why does resync-cache uses LRU, rather than a queue, as its mechanism.
1988wzc at gmail.com
Thu Feb 2 16:12:36 CET 2012
2012/1/29 carlos_wang <1988wzc at gmail.com>
> Hi all:
> 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?
> Thanks in advance.
Blocks may be "resynced" by new application writes as well.
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the drbd-dev