Randomization in hastd(8) synchronization thread

Mon May 23 21:11:30 UTC 2011

On 5/21/2011 8:57 AM, Pawel Jakub Dawidek wrote:
> Hmm, hastd keeps separate bitmap for synchronization. It is stored in
> am_syncmap field. Blocks that are dirtied during regular writes should
> not effect on synchronization bitmap and synchronization progress.

Possibly, but this policy is not very appropriate for slow links. Please 
see my other patch, which only dirties blocks on write.

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
Tel: +1-646-651-1110
Fax: +1-866-857-6942
Web: http://www.sippysoft.com
MSN: sales at sippysoft.com
Skype: SippySoft