From: Matthew Wilcox <matthew@wil.cx>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] Replace inode flush semaphore with a completion
Date: Thu, 26 Jun 2008 20:30:11 -0600 [thread overview]
Message-ID: <20080627023011.GC7703@parisc-linux.org> (raw)
In-Reply-To: <1214455277-6387-3-git-send-email-david@fromorbit.com>
On Thu, Jun 26, 2008 at 02:41:13PM +1000, Dave Chinner wrote:
> Use the new completion flush code to implement the inode
> flush lock. Removes one of the final users of semaphores
> in the XFS code base.
Let's demonstrate converting this one to completions ...
> --- a/fs/xfs/xfs_iget.c
> +++ b/fs/xfs/xfs_iget.c
> @@ -216,7 +216,7 @@ finish_inode:
> mrlock_init(&ip->i_iolock, MRLOCK_BARRIER, "xfsio", ip->i_ino);
> init_waitqueue_head(&ip->i_ipin_wait);
> atomic_set(&ip->i_pincount, 0);
> - initnsema(&ip->i_flock, 1, "xfsfino");
> + init_completion_flush(&ip->i_flush);
+ init_completion(&ip->i_flush);
+ complete(&ip->i_flush);
>
> if (lock_flags)
> xfs_ilock(ip, lock_flags);
> @@ -776,25 +776,24 @@ xfs_isilocked(
> #endif
>
> /*
> - * The following three routines simply manage the i_flock
> - * semaphore embedded in the inode. This semaphore synchronizes
> - * processes attempting to flush the in-core inode back to disk.
> + * Manage the i_flush queue embedded in the inode. This completion
> + * queue synchronizes processes attempting to flush the in-core
> + * inode back to disk.
> */
> void
> xfs_iflock(xfs_inode_t *ip)
> {
> - psema(&(ip->i_flock), PINOD|PLTWAIT);
> + completion_flush_start(&ip->i_flush);
+ wait_for_completion(&ip->i_flush);
> }
>
> int
> xfs_iflock_nowait(xfs_inode_t *ip)
> {
> - return (cpsema(&(ip->i_flock)));
> + return completion_flush_start_nowait(&ip->i_flush);
This is where you need a new function ...
+ return nowait_for_completion(&ip->i_flush);
Yes, we probably need a better name for the down_trylock() equivalent.
> }
>
> void
> xfs_ifunlock(xfs_inode_t *ip)
> {
> - ASSERT(issemalocked(&(ip->i_flock)));
> - vsema(&(ip->i_flock));
> + complete(&ip->i_flush);
Yep.
> }
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index bedc661..81e2040 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -2630,7 +2630,6 @@ xfs_idestroy(
> xfs_idestroy_fork(ip, XFS_ATTR_FORK);
> mrfree(&ip->i_lock);
> mrfree(&ip->i_iolock);
> - freesema(&ip->i_flock);
>
> #ifdef XFS_INODE_TRACE
> ktrace_free(ip->i_trace);
> @@ -3048,10 +3047,10 @@ cluster_corrupt_out:
> /*
> * xfs_iflush() will write a modified inode's changes out to the
> * inode's on disk home. The caller must have the inode lock held
> - * in at least shared mode and the inode flush semaphore must be
> - * held as well. The inode lock will still be held upon return from
> + * in at least shared mode and the inode flush completion must be
> + * active as well. The inode lock will still be held upon return from
> * the call and the caller is free to unlock it.
> - * The inode flush lock will be unlocked when the inode reaches the disk.
> + * The inode flush will be completed when the inode reaches the disk.
> * The flags indicate how the inode's buffer should be written out.
> */
> int
> @@ -3070,7 +3069,7 @@ xfs_iflush(
> XFS_STATS_INC(xs_iflush_count);
>
> ASSERT(xfs_isilocked(ip, XFS_ILOCK_EXCL|XFS_ILOCK_SHARED));
> - ASSERT(issemalocked(&(ip->i_flock)));
> + ASSERT(completion_flush_inprogress(&ip->i_flush));
is_complete()?
> ASSERT(ip->i_d.di_format != XFS_DINODE_FMT_BTREE ||
> ip->i_d.di_nextents > ip->i_df.if_ext_max);
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-06-27 2:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 4:41 [PATCH 0/6] Remove most users of semaphores from XFS Dave Chinner
2008-06-26 4:41 ` [PATCH 1/6] Extend completions to provide XFS object flush requirements Dave Chinner
2008-06-26 7:46 ` Christoph Hellwig
2008-06-26 11:21 ` Dave Chinner
2008-06-26 13:07 ` Christoph Hellwig
2008-06-26 13:18 ` Dave Chinner
2008-06-26 11:26 ` Matthew Wilcox
2008-06-26 11:32 ` Dave Chinner
2008-06-26 11:42 ` Matthew Wilcox
2008-06-26 12:21 ` Dave Chinner
2008-06-26 12:40 ` Matthew Wilcox
2008-06-26 12:49 ` Christoph Hellwig
2008-06-26 13:02 ` Dave Chinner
2008-06-26 20:33 ` Daniel Walker
2008-06-27 1:52 ` Dave Chinner
2008-06-27 2:24 ` Matthew Wilcox
2008-06-27 3:26 ` Daniel Walker
2008-06-27 9:15 ` Christoph Hellwig
2008-06-27 14:37 ` Daniel Walker
2008-06-26 4:41 ` [PATCH 2/6] Replace inode flush semaphore with a completion Dave Chinner
2008-06-27 2:30 ` Matthew Wilcox [this message]
2008-06-27 4:13 ` Dave Chinner
2008-06-26 4:41 ` [PATCH 3/6] Replace dquot " Dave Chinner
2008-06-26 4:41 ` [PATCH 4/6] Replace the XFS buf iodone " Dave Chinner
2008-06-26 7:41 ` Christoph Hellwig
2008-06-26 4:41 ` [PATCH 5/6] Remove the sema_t from XFS Dave Chinner
2008-06-26 4:41 ` [PATCH 6/6] Clean up stale references to semaphores Dave Chinner
2008-06-26 7:47 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080627023011.GC7703@parisc-linux.org \
--to=matthew@wil.cx \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox