Re: [PATCH 1/6] xfs: introduce mmap/truncate lock

To:	Dave Chinner <david@xxxxxxxxxxxxx>
Subject:	Re: [PATCH 1/6] xfs: introduce mmap/truncate lock
From:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:	Wed, 18 Feb 2015 16:41:39 -0800
Cc:	xfs@xxxxxxxxxxx
Delivered-to:	xfs@xxxxxxxxxxx
In-reply-to:	<1423083859-28439-2-git-send-email-david@xxxxxxxxxxxxx>
References:	<1423083859-28439-1-git-send-email-david@xxxxxxxxxxxxx> <1423083859-28439-2-git-send-email-david@xxxxxxxxxxxxx>
User-agent:	Mutt/1.5.23 (2014-03-12)

Is there any real benefit hiding this lock behding the ilock/ilock
wrappers over just acquiring it manually?

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH 0/6 V2] xfs: introduce mmap/truncate lock, Dave Chinner [PATCH 6/6] xfs: lock out page faults from extent swap operations, Dave Chinner Re: [PATCH 6/6] xfs: lock out page faults from extent swap operations, Brian Foster [PATCH 5/6] xfs: xfs_setattr_size no longer races with page faults, Dave Chinner Re: [PATCH 5/6] xfs: xfs_setattr_size no longer races with page faults, Brian Foster [PATCH 1/6] xfs: introduce mmap/truncate lock, Dave Chinner Re: [PATCH 1/6] xfs: introduce mmap/truncate lock, Brian Foster Re: [PATCH 1/6] xfs: introduce mmap/truncate lock, Christoph Hellwig <= [PATCH 2/6] xfs: use i_mmaplock on read faults, Dave Chinner Re: [PATCH 2/6] xfs: use i_mmaplock on read faults, Brian Foster [PATCH 4/6] xfs: take i_mmap_lock on extent manipulation operations, Dave Chinner Re: [PATCH 4/6] xfs: take i_mmap_lock on extent manipulation operations, Brian Foster [PATCH 3/6] xfs: use i_mmaplock on write faults, Dave Chinner Re: [PATCH 3/6] xfs: use i_mmaplock on write faults, Brian Foster

Previous by Date:	Re: [PATCH] xfs: Introduce permanent async buffer write IO failures, Dave Chinner
Next by Date:	Принят новый регламент, Инна Александровна
Previous by Thread:	Re: [PATCH 1/6] xfs: introduce mmap/truncate lock, Brian Foster
Next by Thread:	[PATCH 2/6] xfs: use i_mmaplock on read faults, Dave Chinner
Indexes:	[Date] [Thread] [Top] [All Lists]