From: Nikolay Borisov <kernel@kyup.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: Failing XFS memory allocation
Date: Thu, 24 Mar 2016 11:42:57 +0200 [thread overview]
Message-ID: <56F3B6A1.4020400@kyup.com> (raw)
In-Reply-To: <20160324093345.GA13569@infradead.org>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-03-24 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 10:15 Failing XFS memory allocation Nikolay Borisov
2016-03-23 12:43 ` Brian Foster
2016-03-23 12:56 ` Nikolay Borisov
2016-03-23 13:10 ` Brian Foster
2016-03-23 15:03 ` Nikolay Borisov
2016-03-23 16:58 ` Brian Foster
2016-03-23 23:00 ` Dave Chinner
2016-03-24 9:20 ` Nikolay Borisov
2016-03-24 21:58 ` Dave Chinner
2016-03-24 9:31 ` Christoph Hellwig
2016-03-24 22:00 ` Dave Chinner
2016-03-24 9:33 ` Christoph Hellwig
2016-03-24 9:42 ` Nikolay Borisov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F3B6A1.4020400@kyup.com \
--to=kernel@kyup.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox