From: Matthew Wilcox <matthew@wil.cx>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] Extend completions to provide XFS object flush requirements
Date: Thu, 26 Jun 2008 05:42:42 -0600 [thread overview]
Message-ID: <20080626114242.GX4392@parisc-linux.org> (raw)
In-Reply-To: <20080626113209.GK11558@disturbed>
On Thu, Jun 26, 2008 at 09:32:09PM +1000, Dave Chinner wrote:
> On Thu, Jun 26, 2008 at 05:26:12AM -0600, Matthew Wilcox wrote:
> > On Thu, Jun 26, 2008 at 02:41:12PM +1000, Dave Chinner wrote:
> > > XFS object flushing doesn't quite match existing completion semantics. It
> > > mixed exclusive access with completion. That is, we need to mark an object as
> > > being flushed before flushing it to disk, and then block any other attempt to
> > > flush it until the completion occurs.
> >
> > This sounds like mutex semantics. Why are the existing mutexes not
> > appropriate for your needs?
>
> Different threads doing wait and complete.
Then let's leave it as a semaphore. You can get rid of the sema_t if
you like, but I don't think that turning completions into semaphores is
a good idea (because it's confusing).
--
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-26 11:41 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 [this message]
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
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=20080626114242.GX4392@parisc-linux.org \
--to=matthew@wil.cx \
--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