| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: iomap infrastructure and multipage writes V5 |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Tue, 28 Jun 2016 15:28:39 +0200 |
| Cc: | Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx, rpeterso@xxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160628002649.GI12670@dastard> |
| References: | <1464792297-13185-1-git-send-email-hch@xxxxxx> <20160628002649.GI12670@dastard> |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Tue, Jun 28, 2016 at 10:26:49AM +1000, Dave Chinner wrote: > Christoph, it look slike there's an ENOSPC+ENOMEM behavioural regression here. > generic/224 on my 1p/1GB RAM VM using a 1k lock size filesystem has > significantly different behaviour once ENOSPC is hit withi this patchset. Works fine on my 1k test setup with 4 CPUs and 2GB RAM. 1 CPU and 1GB RAM runs into the OOM killer, although I haven't checked if that was the case with the old code as well. I'll look into this more later today or tomorrow. |
| Previous by Date: | Re: xfs: untangle the direct I/O and DAX path, fix DAX locking, Boaz Harrosh |
|---|---|
| Next by Date: | Re: iomap infrastructure and multipage writes V5, Christoph Hellwig |
| Previous by Thread: | Re: iomap infrastructure and multipage writes V5, Dave Chinner |
| Next by Thread: | Re: iomap infrastructure and multipage writes V5, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |