linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: 2.6.26-rc5-mm2
Date: Wed, 11 Jun 2008 14:09:02 -0400	[thread overview]
Message-ID: <20080611140902.544e59ec@bree.surriel.com> (raw)
In-Reply-To: <200806101848.22237.nickpiggin@yahoo.com.au>

On Tue, 10 Jun 2008 18:48:21 +1000
Nick Piggin <nickpiggin@yahoo.com.au> wrote:

> > > The tmpfs PageSwapBacked stuff seems rather broken. For
> > > them write_begin/write_end path, it is filemap.c, not shmem.c,
> > > which allocates the page, so its no wonder it goes bug. Will
> > > try to do more testing without shmem.

Fun, so what does shmem_alloc_page do?

> > rikstuff.  Could be that the merge caused a problem?
> 
> Doesn't look like it, but I hadn't followed the changes too closely:
> rather they just need to test loopback over tmpfs.

Does loopback over tmpfs use a different allocation path?

> Is the plan to merge all reclaim changes in a big hit, rather than
> slowly trickle in the different independent changes?

My original plan was to merge them incrementally, but Andrew is
right that we should give the whole set as much testing as
possible.

I have done all the cleanups Andrew asked and fixed the bugs
that I found after that merge/cleanup.  Your bug is the one
I still need to fix before giving Andrew a whole new set of
split LRU patches to merge.

(afterwards, I will go incremental fixes only - the cleanups
he asked for were just too big to do as incrementals)

-- 
All rights reversed.

--
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>

  parent reply	other threads:[~2008-06-11 18:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  5:31 2.6.26-rc5-mm2 Andrew Morton
2008-06-10  6:12 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10  7:28 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10  8:34   ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10  8:48     ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10  9:15       ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 12:34         ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 18:09       ` Rik van Riel [this message]
2008-06-11 23:58         ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-12 19:29           ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-12 21:15             ` 2.6.26-rc5-mm2 (swap_state.c:77) Hugh Dickins
2008-06-13 17:45               ` Rik van Riel
2008-06-13 21:15                 ` Hugh Dickins
2008-06-13 22:03                   ` Rik van Riel
2008-06-10 15:34   ` 2.6.26-rc5-mm2 Lee Schermerhorn
2008-06-10 16:50     ` 2.6.26-rc5-mm2 Hugh Dickins
2008-06-10 10:20 ` 2.6.26-rc5-mm2 lockup up on Intel G33+ICH9R+Core2Duo, -mm1 okay Grant Coady
2008-06-10 18:18   ` Andrew Morton
2008-06-10 21:48     ` Grant Coady
2008-06-10 11:50 ` 2.6.26-rc5-mm2 compile error in vmscan.c Helge Hafting
2008-06-10 12:23   ` Johannes Weiner
2008-06-10 18:37   ` Andrew Morton
2008-06-12  8:13     ` Helge Hafting
2008-06-11  2:26 ` 2.6.26-rc5-mm2 (compile error in mm/memory_hotplug.c) Yasunori Goto
2008-06-11  6:00 ` 2.6.26-rc5-mm2: OOM with 1G free swap Alexey Dobriyan
2008-06-11  6:11   ` Nick Piggin
2008-06-11  6:15   ` Nick Piggin
2008-06-11  6:27   ` Andrew Morton
2008-06-11  6:31     ` Nick Piggin
2008-06-11  6:36     ` KOSAKI Motohiro
2008-06-11  7:31       ` Frederik Deweerdt
2008-06-11 12:57     ` Rik van Riel
2008-06-11 13:44       ` Nick Piggin
2008-06-11 17:56 ` [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Kamalesh Babulal
2008-06-11 18:28   ` Dave Hansen
2008-06-11 18:37     ` Vegard Nossum
2008-06-12  6:55       ` Kamalesh Babulal

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=20080611140902.544e59ec@bree.surriel.com \
    --to=riel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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