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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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@fromorbit.com>
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?

_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs

References:
- [PATCH 0/6 V2] xfs: introduce mmap/truncate lock
  - From: Dave Chinner
- [PATCH 1/6] xfs: introduce mmap/truncate lock
  - From: Dave Chinner

Prev by Date: Re: [PATCH] xfs: Introduce permanent async buffer write IO failures
Next by Date: Re: [PATCH] [RFC] xfs: add RENAME_WHITEOUT support
Previous by thread: Re: [PATCH 1/6] xfs: introduce mmap/truncate lock
Next by thread: [PATCH 2/6] xfs: use i_mmaplock on read faults
Index(es):
- Date
- Thread

[Index of Archives] [Linux XFS Devel] [Linux Filesystem Development] [Filesystem Testing] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux