From: Joe Thornber Date: Fri, 27 Jul 2012 14:08:09 +0000 (+0100) Subject: dm persistent data: stop using dm_bm_unlock_move when shadowing blocks in tm X-Git-Tag: v3.6-rc1~56^2~25 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3c9ad9bd87b03032999ddbeb44bdf7938f7dbd57;p=pandora-kernel.git dm persistent data: stop using dm_bm_unlock_move when shadowing blocks in tm Stop using dm_bm_unlock_move when shadowing blocks in the transaction manager as an optimisation and remove the function as it is then no longer used. Some code, such as the space maps, keeps using on-disk data structures from the previous transaction. It can do this because blocks won't be reallocated until the subsequent transaction. Using dm_bm_unlock_move to copy blocks sounds like a win, but it forces a synchronous read should the old block be accessed. Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer Signed-off-by: Alasdair G Kergon --- Reading git-diff-tree failed