linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rik van Riel <riel@redhat.com>
Subject: Re: [-mm][PATCH 0/10]  memory related bugfix set for 2.6.26-rc5-mm3 v2
Date: Wed, 25 Jun 2008 11:09:31 -0400	[thread overview]
Message-ID: <1214406571.7010.21.camel@lts-notebook> (raw)
In-Reply-To: <20080625185717.D84C.KOSAKI.MOTOHIRO@jp.fujitsu.com>

On Wed, 2008-06-25 at 18:59 +0900, KOSAKI Motohiro wrote:
> Hi, Andrew and mm guys!
> 
> this is mm related fixes patchset for 2.6.26-rc5-mm3 v2.
> 
> Unfortunately, this version has several bugs and 
> some bugs depend on each other.
> So, I collect, sort, and fold these patchs.
> 
> 
> btw: I wrote "this patch still crashed" last midnight.
> but it works well today.
> umm.. I was dreaming?

Yes.  I ran my stress load with Nishimura-san's cpuset migration test on
x86_64 and ia64 platforms overnight.  I didn't have all of the memcgroup
patches applied--just the unevictable lru related patches.  Tests ran
for ~19 hours--including 70k-80k passes through the cpuset migration
test--until I shut them down w/o error.  

OK, I did see two oom kills on the ia64.  My stress load was already
pretty close to edge, but they look suspect because I still had a couple
of MB free on each node according to the console logs.  The system did
seem to choose a reasonable task to kill, tho'--a memtoy test that locks
down 10s of GB of memory.

> 
> Anyway, I believe this patchset improve robustness and
> provide better testing baseline.
> 
> enjoy!

I'll restart the tests with this series.

> 
> 
> Andrew, this patchset is my silver-spoon.
> if you like it, I'm glad too.
> 
> 
> 

--
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-25 15:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  9:59 KOSAKI Motohiro
2008-06-25 10:01 ` [-mm][PATCH 1/10] fix UNEVICTABLE_LRU and !PROC_PAGE_MONITOR build KOSAKI Motohiro
2008-07-03  5:36   ` Andrew Morton
2008-07-03  6:02     ` KOSAKI Motohiro
2008-07-03 13:16       ` Rik van Riel
2008-06-25 10:02 ` [-mm][PATCH 2/10] fix printk in show_free_areas() KOSAKI Motohiro
2008-06-25 10:03 ` [-mm][PATCH 3/10] fix munlock page table walk - now requires 'mm' KOSAKI Motohiro
2008-06-25 10:04 ` [-mm][PATCH 4/10] fix migration_entry_wait() for speculative page cache KOSAKI Motohiro
2008-06-25 10:05 ` [-mm][PATCH 5/10] collect lru meminfo statistics from correct offset KOSAKI Motohiro
2008-06-25 10:06 ` [-mm][PATCH 6/10] fix incorrect Mlocked field of /proc/meminfo KOSAKI Motohiro
2008-06-25 10:07 ` [-mm][PATCH 7/10] prevent incorrect oom under split_lru KOSAKI Motohiro
2008-06-25 10:09 ` [-mm][PATCH 8/10] fix shmem page migration incorrectness on memcgroup KOSAKI Motohiro
2008-06-27  5:08   ` MinChan Kim
2008-06-27  5:41     ` KOSAKI Motohiro
2008-06-27  7:57       ` MinChan Kim
2008-06-27  8:52         ` KAMEZAWA Hiroyuki
2008-06-27  9:29           ` Daisuke Nishimura
2008-06-27 10:13           ` MinChan Kim
2008-06-27 12:24           ` kamezawa.hiroyu
2008-06-25 10:10 ` [-mm][PATCH 9/10] memcg: fix mem_cgroup_end_migration() race KOSAKI Motohiro
2008-06-25 10:53   ` Daisuke Nishimura
2008-06-25 10:11 ` [-mm][PATCH 10/10] putback_lru_page()/unevictable page handling rework v4 KOSAKI Motohiro
2008-06-25 10:14   ` KOSAKI Motohiro
2008-06-25 22:13     ` Andrew Morton
2008-06-26  1:31       ` KOSAKI Motohiro
2008-06-25 16:29   ` Lee Schermerhorn
2008-06-26  8:08     ` KOSAKI Motohiro
2008-06-25 15:09 ` Lee Schermerhorn [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=1214406571.7010.21.camel@lts-notebook \
    --to=lee.schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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