From: Dave Chinner <david@fromorbit.com>
To: Nikolay Borisov <kernel@kyup.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: Failing XFS memory allocation
Date: Fri, 25 Mar 2016 08:58:58 +1100 [thread overview]
Message-ID: <20160324215858.GE11812@dastard> (raw)
In-Reply-To: <56F3B157.2060505@kyup.com>
On Thu, Mar 24, 2016 at 11:20:23AM +0200, Nikolay Borisov wrote:
> On 03/24/2016 01:00 AM, Dave Chinner wrote:
> > As it is, yes, the memory allocation problem is with the in-core
> > extent tree, and we've known about it for some time. The issue is
> > that as memory gets fragmented, the top level indirection array
> > grows too large to be allocated as a contiguous chunk. When this
> > happens really depends on memory load, uptime and the way the extent
> > tree is being modified.
>
> And what about the following completely crazy idea of switching order >
> 3 allocations to using vmalloc? I know this would incur heavy
> performance hit, but other than that would it cause correctness issues?
> Of course I'm not saying this should be implemented in upstream rather
> whether it's worth it having a go for experimenting with this idea.
It's not an option as many supported platforms which have extremely
limited vmalloc space.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-03-24 21:59 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 [this message]
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
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=20160324215858.GE11812@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=kernel@kyup.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.