Date: Mon, 23 May 2011 14:11:27 -0700 From: Maxim Sobolev <sobomax@sippysoft.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: "current@freebsd.org" <current@FreeBSD.ORG> Subject: Re: Randomization in hastd(8) synchronization thread Message-ID: <4DDACD7F.7040704@sippysoft.com> In-Reply-To: <20110521155755.GC3326@garage.freebsd.pl> References: <4DD2CEE7.1070805@sippysoft.com> <20110521155755.GC3326@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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@sippysoft.com Skype: SippySoft
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DDACD7F.7040704>