xfs
[Top] [All Lists]

Re: [Patch] Per iclog callback chain lock

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [Patch] Per iclog callback chain lock
From: David Chinner <dgc@xxxxxxx>
Date: Tue, 8 Apr 2008 08:17:28 +1000
Cc: David Chinner <dgc@xxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
In-reply-to: <20080407125111.GB27350@infradead.org>
References: <20080401231348.GT103491721@sgi.com> <20080407125111.GB27350@infradead.org>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Mon, Apr 07, 2008 at 08:51:11AM -0400, Christoph Hellwig wrote:
> Looks good.  You might want to kill ic_callback_tail while you're at it
> as it's a write-only struct member.

No, it's not a write-only member. xlog_notify() queues to the tail
by doing:

    410                 cb->cb_next = NULL;
    411                 *(iclog->ic_callback_tail) = cb;
    412                 iclog->ic_callback_tail = &(cb->cb_next);

So we can't remove it. Changing the callback chain to use a
struct list_head makes more sense, but that's a separate patch....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group


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