xfs: do exact log space wakeups in xlog_ungrant_log_space
authorChristoph Hellwig <hch@infradead.org>
Mon, 20 Feb 2012 02:31:21 +0000 (02:31 +0000)
committerBen Myers <bpm@sgi.com>
Thu, 23 Feb 2012 04:17:00 +0000 (22:17 -0600)
The only reason that xfs_log_space_wake had to do opportunistic wakeups
was that the old xfs_log_move_tail calling convention didn't allow for
exact wakeups when not updating the log tail LSN.  Since this issue has
been fixed we can do exact wakeups now.

Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Ben Myers <bpm@sgi.com>
fs/xfs/xfs_log.c

index 372642d3987205ab79ec3c65792a8f69686002d1..9161e8a76e777382933185a10b26dc991a3b5f52 100644 (file)
@@ -2748,7 +2748,7 @@ xlog_ungrant_log_space(xlog_t          *log,
 
        trace_xfs_log_ungrant_exit(log, ticket);
 
-       xfs_log_space_wake(log->l_mp, true);
+       xfs_log_space_wake(log->l_mp, false);
 }
 
 /*