| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 4/5] xfs: push the ilock into xfs_zero_eof |
| From: | Mark Tinguely <tinguely@xxxxxxx> |
| Date: | Mon, 02 Apr 2012 15:39:45 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20120327143826.792184421@xxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20120327143445.196524266@xxxxxxxxxxxxxxxxxxxxxx> <20120327143826.792184421@xxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120122 Thunderbird/9.0 |
On 03/27/12 09:34, Christoph Hellwig wrote: Instead of calling xfs_zero_eof with the ilock held only take it internally for the minimall required critical section around xfs_bmapi_read. This also requires changing the calling convention for xfs_zero_last_block slightly. The actual zeroing operation is still serialized by the iolock, which must be taken exclusively over the call to xfs_zero_eof. We could in fact use a shared lock for the xfs_bmapi_read calls as long as the extent list has been read in, but given that we already hold the iolock exclusively there is little reason to micro optimize this further. Reviewed-by: Dave Chinner<dchinner@xxxxxxxxxx> Signed-off-by: Christoph Hellwig<hch@xxxxxx> Looks good. Reviewed-by: Mark Tinguely <tinguely@xxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 3/5] xfs: reduce ilock hold times in xfs_setattr_size, Mark Tinguely |
|---|---|
| Next by Date: | Re: [ANNOUNCE] XFS Developers meeting in San Francisco, April 3rd, Eric Sandeen |
| Previous by Thread: | Re: [PATCH 3/5] xfs: reduce ilock hold times in xfs_setattr_size, Mark Tinguely |
| Next by Thread: | Re: [ANNOUNCE] XFS Developers meeting in San Francisco, April 3rd, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |