dm-block-manager unused variable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



in  file dm-block-manager.c,  in function dm_block_manager_create(),the variable cache_size unused? Any design considerations?

------------------------------------------------------------------
发件人:Mike Snitzer <snitzer@xxxxxxxxxx>
发送时间:2014年11月2日(星期日) 02:46
收件人:lilofile <lilofile@xxxxxxxxxx>
抄 送:dm-devel <dm-devel@xxxxxxxxxx>
主 题:Re:  dm-thin  COMMIT_PERIOD problem


On Sat, Nov 01 2014 at 10:40am -0400,
lilofile <lilofile@xxxxxxxxxx> wrote:

> In dm-thin.c,COMMIT_PERIOD is set HZ, I think this value has a  impact on system impact,too frequent commit will reduce the write performance of the system?
> other method which it is submitted by  the total size of dirty data   is feasible?

It only issues IO if changes have occured.  It isn't writing to disk
every second unless changes need to get to disk anyway.

(There was a bug where it _did_ write the metadata superblock every
second even when it wasn't needed.. since fixed with this commit:
http://git.kernel.org/linus/4d1662a30 )

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel





[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux