From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, npiggin@kernel.dk, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: flush vmap aliases when mapping fails
Date: Thu, 17 Mar 2011 10:24:18 -0400 [thread overview]
Message-ID: <20110317142418.GB32673@infradead.org> (raw)
In-Reply-To: <20110310224945.GA15097@dastard>
On Fri, Mar 11, 2011 at 09:49:45AM +1100, Dave Chinner wrote:
> > IMHO this should be done by vm_map_ram internally. If we can't get the
> > core code fixes we can put this in as a last resort.
>
> OK. The patch was done as part of the triage for this bug:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=27492
>
> where the vmalloc space on 32 bit systems is getting exhausted. I
> can easily move this flush-and-retry into the vmap code.
Looks like we're not going to make any progress on the VM side for this,
so I think we'll need the XFS variant for 2.6.39.
Reviewed-by: Christoph Hellwig <hch@lst.de>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-17 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1299713876-7747-1-git-send-email-david@fromorbit.com>
2011-03-10 7:37 ` [PATCH] xfs: flush vmap aliases when mapping fails Christoph Hellwig
2011-03-10 22:49 ` Dave Chinner
2011-03-17 14:24 ` Christoph Hellwig [this message]
2011-03-21 12:25 ` Johannes Weiner
2011-03-22 12:57 ` Johannes Weiner
2011-03-27 23:54 ` Dave Chinner
2011-03-18 14:24 ` Johannes Weiner
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=20110317142418.GB32673@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).