| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Failing XFS memory allocation |
| From: | Nikolay Borisov <kernel@xxxxxxxx> |
| Date: | Thu, 24 Mar 2016 11:42:57 +0200 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160324093345.GA13569@xxxxxxxxxxxxx> |
| References: | <56F26CCE.6010502@xxxxxxxx> <20160324093345.GA13569@xxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
On 03/24/2016 11:33 AM, Christoph Hellwig wrote: > Hi Nikolay, > > can you give the patch below a spin? While it doesn't solve the root > cause it makes many typical uses of kmem_realloc behave less badly, > so it should help with at least some of the less dramatic cases of very > fragmented files: > Sure, however I just checked some other servers with analogical setup and there are files which even larger extents (the largest I saw was 2 millions) so I guess in this particular case the memory was fragmented and compaction as invoked from the page allocator couldn't satisfy it. So I don't know if it will help in my particular case but in any case I will give it a go. Thanks |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Failing XFS memory allocation, Christoph Hellwig |
|---|---|
| Next by Date: | Re: XFS hung task in xfs_ail_push_all_sync() when unmounting FS after disk failure/recovery, Carlos Maiolino |
| Previous by Thread: | Re: Failing XFS memory allocation, Christoph Hellwig |
| Next by Thread: | [PATCH] xfs: improve kmem_realloc, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |