| To: | Geoffrey Wehrman <gwehrman@xxxxxxx> |
|---|---|
| Subject: | Re: Issues with delalloc->real extent allocation |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 18 Jan 2011 15:40:09 -0500 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20110118143000.GB8803@xxxxxxx> |
| References: | <20110114002900.GF16267@dastard> <20110114164016.GB30134@xxxxxxx> <20110114225907.GH16267@dastard> <20110115041629.GC11968@xxxxxxx> <20110117051827.GL16267@dastard> <20110117143708.GE11968@xxxxxxx> <20110118002437.GS28803@dastard> <20110118143000.GB8803@xxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Jan 18, 2011 at 08:30:00AM -0600, Geoffrey Wehrman wrote: > Glad you were able to understand what I meant. Something I didn't think > of earlier though: What happens when I try to use an 8 GB on a system > with only 4 GB of memory? I'm not really worried about this pathological > case, but I do wonder what the effects will be of allocating what could > be significant quantities of memory in .aio_write. I think for large regions we'd be much better off to only zero the blocks on disk, not in-memory - for example like the code in xfs_zero_remaining_bytes does. |
| Previous by Date: | [PATCH] xfs_bmap_add_extent_delay_real should set br_startblock to nullstartblock, Ben Myers |
|---|---|
| Next by Date: | Re: Issues with delalloc->real extent allocation, Christoph Hellwig |
| Previous by Thread: | Re: Issues with delalloc->real extent allocation, Geoffrey Wehrman |
| Next by Thread: | Re: Issues with delalloc->real extent allocation, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |