From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
Brian Matheson <bmath@paperspace.com>,
linux-xfs@vger.kernel.org
Subject: Re: memory allocation deadlock
Date: Sun, 18 Jun 2017 00:16:17 -0700 [thread overview]
Message-ID: <20170618071617.GA26968@infradead.org> (raw)
In-Reply-To: <20170616193740.GH5421@birch.djwong.org>
On Fri, Jun 16, 2017 at 12:37:40PM -0700, Darrick J. Wong wrote:
> memory and make the problems occur less frequently, as you've also
> observed. However, that leaves the underlying problem, which is that we
> need to break up the in-core cache into a tree(ish) structure of single
> pages. Maybe that'll happen for 4.14 (Christoph?).
Working on it, but it will be a big and potentially contentious change,
so stay tuned.
prev parent reply other threads:[~2017-06-18 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 17:10 memory allocation deadlock Brian Matheson
2017-06-16 18:14 ` Eric Sandeen
2017-06-16 18:57 ` Brian Matheson
2017-06-16 19:12 ` Eric Sandeen
2017-06-16 19:37 ` Darrick J. Wong
2017-06-18 7:16 ` Christoph Hellwig [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=20170618071617.GA26968@infradead.org \
--to=hch@infradead.org \
--cc=bmath@paperspace.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).