public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Daniel Walker <dwalker@mvista.com>
Cc: Dave Chinner <david@fromorbit.com>,
	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 20:24:07 -0600	[thread overview]
Message-ID: <20080627022407.GB7703@parisc-linux.org> (raw)
In-Reply-To: <1214512405.21035.110.camel@localhost.localdomain>

On Thu, Jun 26, 2008 at 01:33:25PM -0700, Daniel Walker wrote:
> I think there is some basis to make the changes that you have here.
> Specifically this email and thread,
> 
> http://lkml.org/lkml/2008/4/15/232

You've completely missed the point.  The current semaphore code is
_more_ efficient than the current completion code.  I'm very comfortable
having two APIs here, one for completion-like semantics and one for
mutex-like semantics.  Confusing them like this makes no sense at all.

> However, I don't like how your implementing this as specifically a
> "flush" mechanism for XFS, and the count is limited to just 1 .. There
> are several other places that do this kind of counting with semaphores,
> and have counts above 1..

Then leave them as semaphores.  Really.

-- 
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."

  parent reply	other threads:[~2008-06-27  2:23 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 [this message]
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=20080627022407.GB7703@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=david@fromorbit.com \
    --cc=dwalker@mvista.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