Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Aug 2009 19:20:33 GMT
From:      Aditya Sarawgi <truncs@FreeBSD.org>
To:        Perforce Change Reviews <perforce@FreeBSD.org>
Subject:   PERFORCE change 167905 for review
Message-ID:  <200908271920.n7RJKXW4086378@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=167905

Change 167905 by truncs@aditya on 2009/08/27 19:20:28

	ip->i_next_alloc_goal is often 0 (which means that it
	shouldn't be used), but it was often used.  Using a goal of 0 
	gives preferernce to early blocks.

Affected files ...

.. //depot/projects/soc2009/soc_ext2fs/src/sys/fs/ext2fs/ext2_alloc.c#2 edit

Differences ...

==== //depot/projects/soc2009/soc_ext2fs/src/sys/fs/ext2fs/ext2_alloc.c#2 (text+ko) ====

@@ -443,7 +443,7 @@
 	/* if the next block is actually what we thought it is,
 	   then set the goal to what we thought it should be
 	*/
-	if(ip->i_next_alloc_block == lbn)
+	if(ip->i_next_alloc_block == lbn && && ip->i_next_alloc_goal != 0)
 		return ip->i_next_alloc_goal;
 
 	/* now check whether we were provided with an array that basically



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200908271920.n7RJKXW4086378>