All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: xfs@oss.sgi.com
Subject: Re: Excessive xfs_inode allocations trigger OOM killer
Date: Tue, 20 Sep 2016 14:51:47 -0700	[thread overview]
Message-ID: <20160920215147.GA31614@infradead.org> (raw)
In-Reply-To: <87a8f2pd2d.fsf@mid.deneb.enyo.de>

Hi Florian,

can you check if you have CONFIG_COMPACTION enabled in your kernel
config?  There have been some regressions in the VM code lately that
made me see similar OOM killer rampage runs, which went away after I
followed some linux-mm advise to turn it on.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2016-09-20 21:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 19:48 Excessive xfs_inode allocations trigger OOM killer Florian Weimer
2016-09-20 20:30 ` Dave Chinner
2016-09-20 20:56   ` Florian Weimer
2016-09-20 21:46     ` Dave Chinner
2016-09-21  5:45       ` Florian Weimer
2016-09-21  5:45         ` Florian Weimer
2016-09-21  5:45       ` Florian Weimer
2016-09-21  8:04       ` Michal Hocko
2016-09-21  8:06         ` Michal Hocko
2016-09-21  8:06           ` Michal Hocko
2016-09-26 17:33         ` Florian Weimer
2016-09-26 17:33           ` Florian Weimer
2016-09-26 20:02           ` Michal Hocko
2016-09-26 20:02             ` Michal Hocko
2016-10-03 17:35             ` Florian Weimer
2016-10-03 17:35               ` Florian Weimer
2016-10-03 17:54               ` Michal Hocko
2016-10-03 17:54                 ` Michal Hocko
2016-09-20 21:51 ` Christoph Hellwig [this message]
2016-09-20 21:54   ` Florian Weimer

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=20160920215147.GA31614@infradead.org \
    --to=hch@infradead.org \
    --cc=fw@deneb.enyo.de \
    --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.