xfs
[Top] [All Lists]

Re: [PATCH 1/6] Extend completions to provide XFS object flush requireme

To: Daniel Walker <dwalker@xxxxxxxxxx>
Subject: Re: [PATCH 1/6] Extend completions to provide XFS object flush requirements
From: Matthew Wilcox <matthew@xxxxxx>
Date: Thu, 26 Jun 2008 20:24:07 -0600
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <1214512405.21035.110.camel@xxxxxxxxxxxxxxxxxxxxx>
References: <1214455277-6387-1-git-send-email-david@xxxxxxxxxxxxx> <1214455277-6387-2-git-send-email-david@xxxxxxxxxxxxx> <1214512405.21035.110.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
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."


<Prev in Thread] Current Thread [Next in Thread>