From: Peter Zijlstra <peterz@infradead.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Andi Kleen <andi@firstfloor.org>,
Minchan Kim <minchan.kim@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [patch v3] swap: virtual swap readahead
Date: Wed, 10 Jun 2009 11:42:56 +0200 [thread overview]
Message-ID: <1244626976.13761.11593.camel@twins> (raw)
In-Reply-To: <20090610085638.GA32511@localhost>
On Wed, 2009-06-10 at 16:56 +0800, Wu Fengguang wrote:
>
> Yes it worked! But then I run into page allocation failures:
>
> [ 340.639803] Xorg: page allocation failure. order:4, mode:0x40d0
> [ 340.645744] Pid: 3258, comm: Xorg Not tainted 2.6.30-rc8-mm1 #303
> [ 340.651839] Call Trace:
> [ 340.654289] [<ffffffff810c8204>] __alloc_pages_nodemask+0x344/0x6c0
> [ 340.660645] [<ffffffff810f7489>] __slab_alloc_page+0xb9/0x3b0
> [ 340.666472] [<ffffffff810f8608>] __kmalloc+0x198/0x250
> [ 340.671786] [<ffffffffa014bf9f>] ? i915_gem_execbuffer+0x17f/0x11e0 [i915]
> [ 340.678746] [<ffffffffa014bf9f>] i915_gem_execbuffer+0x17f/0x11e0 [i915]
Jesse Barnes had a patch to add a vmalloc fallback to those largish kms
allocs.
But order-4 allocs failing isn't really strange, but it might indicate
this patch fragments stuff sooner, although I've seen these particular
failues before.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-10 9:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:01 [patch v3] swap: virtual swap readahead Johannes Weiner
2009-06-09 19:37 ` Johannes Weiner
2009-06-10 5:03 ` Wu Fengguang
2009-06-10 7:45 ` Johannes Weiner
2009-06-10 8:11 ` Wu Fengguang
2009-06-10 8:32 ` KAMEZAWA Hiroyuki
2009-06-10 8:56 ` Wu Fengguang
2009-06-10 9:42 ` Peter Zijlstra [this message]
2009-06-10 9:59 ` Wu Fengguang
2009-06-10 10:05 ` Peter Zijlstra
2009-06-10 11:32 ` Wu Fengguang
2009-06-10 17:25 ` Jesse Barnes
2009-06-11 5:22 ` Wu Fengguang
2009-06-11 10:17 ` Johannes Weiner
2009-06-12 1:59 ` Wu Fengguang
2009-06-15 18:22 ` Johannes Weiner
2009-06-18 9:19 ` Wu Fengguang
2009-06-18 13:01 ` Johannes Weiner
2009-06-19 3:30 ` Wu Fengguang
2009-06-21 18:07 ` Hugh Dickins
2009-06-21 18:37 ` Johannes Weiner
2009-06-10 9:30 ` Johannes Weiner
2009-06-10 6:39 ` KAMEZAWA Hiroyuki
2009-06-11 5:31 ` KAMEZAWA Hiroyuki
2009-06-17 22:41 ` Johannes Weiner
2009-06-18 9:29 ` Wu Fengguang
2009-06-18 13:09 ` Johannes Weiner
2009-06-19 3:17 ` Wu Fengguang
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=1244626976.13761.11593.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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).