| To: | "Darrick J. Wong" <darrick.wong@xxxxxxxxxx> |
|---|---|
| Subject: | Re: stop using ioends for direct write completions |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Fri, 29 Jan 2016 09:01:57 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160128223131.GD6431@xxxxxxxxxxxxxxxx> |
| References: | <1452766237-2314-1-git-send-email-hch@xxxxxx> <20160128131656.GB14876@xxxxxxxxxxxxx> <20160128205333.GF20038@xxxxxxxxxxxxxxxx> <20160128211056.GA27287@xxxxxx> <20160128215853.GC6431@xxxxxxxxxxxxxxxx> <20160128220255.GA28202@xxxxxx> <20160128223131.GD6431@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Thu, Jan 28, 2016 at 02:31:31PM -0800, Darrick J. Wong wrote: > As for the generic/154... the code on github is sadly not very bisectable, > other than to say that until yesterday I was still tacking new code onto > the end of the patchset. > > That said, I was seeing occasional hangs in generic/154 (I needed to roll > the transactions between key parts of wrapping up a CoW) and they seem to > have gone away, so it's possible that I've fixed it already. I'm seeing them with a HEAD of 9628553acf5ff4225e047d580094ffab64605f50, but only when using NFS. If you've got something newer feel free to push it out, otherwise I'll have to spend some more time trying to figure out what's going on with this version. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: stop using ioends for direct write completions, Darrick J. Wong |
|---|---|
| Next by Date: | Random write result differences between RAID device and XFS, Christian Affolter |
| Previous by Thread: | Re: stop using ioends for direct write completions, Darrick J. Wong |
| Next by Thread: | Re: stop using ioends for direct write completions, Brian Foster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |